Release 7.0.2 - #468
Merged
Merged
Conversation
workflow_run events only expose head_sha/head_branch for the ref rc-release.yml was dispatched WITH (e.g. development), never the releases/** branch its own prepare-branch job creates during the run. Trusting those fields meant every automatic smoke run checked out development (still at the last real release's version), saw a non-RC pubspec version, and silently skipped — since rc-smoke.yml was added in #446 (Apr 26, 2026), the automatic path has never actually smoke-tested a real RC. Fix: resolve the actual RC from the GitHub prerelease that create-prerelease just published (tag_name + created_at, sanity checked against the triggering run's completion time within 30 min), derive the release branch from that tag using the same naming convention rc-release.yml computes, and check that branch out instead. Manual workflow_dispatch path (rc_version/release_branch inputs) is unaffected — it already worked correctly, as verified by manually running it for 6.18.1-rc1/rc2. No new secrets needed — reading releases via the API only requires the default GITHUB_TOKEN's existing read access. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…-resolution Fix rc-smoke.yml resolving the wrong branch on automatic trigger
…tecture. (#466) [DELIVERY-125863] Migrate Flutter plugin to AppsFlyer SDK 7 RPC architecture. Route core APIs through af-api/af-events RPC bridges on Android and iOS, adopt the SDK 7 init + session-ready start model, remove SDK 6 APIs that no longer exist natively, bump native dependencies to 7.0.1, raise iOS minimum to 13.0, and reorganize public documentation.
rc-smoke rsyncs example/ sources but keeps the template pubspec, which still allowed Dart 2.12 while example uses super-parameters. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
🚀 Ready for Production ReleaseThe release branch has been updated:
Next Steps
|
promote-release.yml rewrote the Dart PLUGIN_VERSION but never staged lib/, so 7.0.2 would have shipped reporting 7.0.2-rc1 from the public pluginVersion getter. Stage lib/ and restore the constant. Add scripts/verify-version-consistency.sh, asserting that pubspec.yaml, the three plugin version constants, the podspec and Package.swift all agree. It runs in promote before the commit and in production-release inside the publish job, because the job gate above it is always() and so a failure in validate-release would not stop the publish. The plugin version unit test now reads pubspec.yaml instead of a literal, so it tracks the version the pipeline writes and still fails on real drift. Co-authored-by: Cursor <cursoragent@cursor.com>
af-dudka
requested review from
Dani-Koza-AF,
Kobikg78,
al-af,
pazlavi and
tlozovyi-af
August 28, 2026 07:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Production Release 7.0.2
Status: ✅ Ready for manual merge
Version updated: 7.0.2-rc1 → 7.0.2
Release 7.0.2
This PR was opened by the RC workflow.
Next steps: