Set up Flutter in the publish jobs - #530
Merged
Merged
Conversation
Both publish jobs installed only the Dart SDK, so `dart pub publish` could not resolve the `flutter` SDK dependency and exited 69 before uploading. The v3.4.3 and firebase-v2.1.4 tags failed this way and nothing reached pub.dev. Uses the same pinned Flutter setup as the other jobs and publishes with `flutter pub publish`. Drops `-v`, whose output exceeded the step log limit and truncated the actual error. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
4 tasks
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
1 participant
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.
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Bug fix (CI release automation).
Both publish jobs install only the Dart SDK via
dart-lang/setup-dart, then rundart pub publish. Because both packages depend onflutterfrom the SDK, dependency resolution fails before anything is uploaded and the step exits 69. Thev3.4.3andfirebase-v2.1.4tags both failed this way; neither package reached pub.dev.This path was introduced in the (still unreleased) CI modernization, so no previous release exercised it.
The
-vflag also made this hard to diagnose: its dependency-resolution dump exceeded the step log limit, so the log was truncated before the actual error.🆕 What is the new behavior (if this is a feature change)?
The publish jobs set up Flutter with the same pinned
FLUTTER_VERSIONthe other jobs use and publish withflutter pub publish -f. OIDC trusted publishing is unaffected — it relies on the job'sid-token: writepermission, not on which action installed the SDK. Verbose output is dropped so a future failure is readable.💥 Does this PR introduce a breaking change?
No.
🐛 Recommendations for testing
Only reachable on a tag push, so PR checks cover the workflow parsing but not the publish step itself. Real verification is re-pointing the
v3.4.3/firebase-v2.1.4tags at this commit and confirming both packages land on pub.dev. No changelog entry: the existing unreleased "Modernizes GitHub Actions CI" bullet already covers this code, which has never shipped.📝 Links to relevant issues/docs
Failed runs: v3.4.3, firebase-v2.1.4.
🤔 Checklist before submitting
🤖 Generated with Claude Code