Skip to content

fix(sync): keep mirror-only CI out of personaclick/flutter-sdk - #349

Merged
Xyzcancer merged 1 commit into
masterfrom
fix/flutter-sync-drop-mirror-ci
Aug 3, 2026
Merged

fix(sync): keep mirror-only CI out of personaclick/flutter-sdk#349
Xyzcancer merged 1 commit into
masterfrom
fix/flutter-sync-drop-mirror-ci

Conversation

@Xyzcancer

Copy link
Copy Markdown
Contributor

No description provided.

The mirror is a generated artifact: quality and versioning decisions belong to
rees46/flutter-sdk, which is green before a sync ever starts. Three workflows are
now stripped on the way over.

checks.yaml cannot pass there — the rename lengthens import lines past 80 cols, so
dart format rewraps 12 files. integration-android.yaml drives Patrol against
api.personaclick.com, where the example's hardcoded demo shop c1140c... does not
exist, and the example APK does not build anyway (google-services.json is deleted
while build.gradle.kts still applies the google-services plugin). version.yaml
would run semantic-release over the mirror's own history, where every commit is
'feat(release): sync (#N)' — a feat, so it would invent a minor bump and drift
from the version this sync delivers.

What is left in the mirror is deploy.yaml + publish.yaml: see the synced version,
tag it, publish to pub.dev.

Also corrects the header comment: the engine deletes before renaming, so the
deletions are source paths.
@Xyzcancer
Xyzcancer merged commit 7e2f924 into master Aug 3, 2026
1 check passed
@Xyzcancer
Xyzcancer deleted the fix/flutter-sync-drop-mirror-ci branch August 3, 2026 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant