Repository navigation
ci: pin the Flutter version in build.yaml - #45
Merged
rickdijk merged 1 commit intoSep 23, 2026
Merged
Conversation
Every subosito/flutter-action step set channel: "stable" with no flutter-version, so CI ran whatever stable happened to be on the day. That is what let CI go red with no commit to the repo (FPL-34). Add a workflow-level FLUTTER_VERSION env var, matching the version flutter_cache_manager pins, and reference it from every flutter-action step. Also drop architecture: x64 from the two macos-latest jobs, which run on Apple Silicon, not x64. Update AGENTS.md to state the pinned version and how to bump it. Verified locally at Flutter 3.47.4: dart format, flutter analyze, flutter test, and the Android example release build are all clean, which also regenerated analysis_options.yaml (build dir excludes) and example/linux/flutter/generated_plugins.cmake (FFI plugin list) to match current Flutter tooling. Fixes FPL-32. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
rickdijk
deleted the
rick/fpl-32-octo_image-pin-the-flutter-version-in-ci
branch
September 23, 2026 18:16
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...)
CI-only change: pin the Flutter version used in
.github/workflows/build.yaml.Every
subosito/flutter-actionstep setschannel: "stable"with noflutter-version, so CI runs whateverstablehappens to be on the day. That is exactly what let CI go red with no commit to the repo (FPL-34:stablemoved past the example's old AGP/Kotlin).architecture: x64is also passed on themacos-latestrunners, which are Apple Silicon, not x64.🆕 What is the new behavior (if this is a feature change)?
env: FLUTTER_VERSION: "3.47.4", matching the versionflutter_cache_managerpins, referenced asflutter-version: ${{ env.FLUTTER_VERSION }}in everysubosito/flutter-actionstep.architecture: x64from the twomacos-latestjobs (build_ios,build_macOS).AGENTS.mdnow states the pinned version and how to bump it.analysis_options.yaml(build dir excludes) andexample/linux/flutter/generated_plugins.cmake(FFI plugin list) to match current Flutter tooling; no analyzer/lint findings turned up.💥 Does this PR introduce a breaking change?
No. CI-only, no
pubspec.yamlversion bump.🐛 Recommendations for testing
Confirm this PR's own
build.yamlrun is green, and check the "Set up Flutter" step logs show Flutter 3.47.4.📝 Links to relevant issues/docs
Closes FPL-32. Follows FPL-34 (green baseline, PR #43). Reference repo:
flutter_cache_manager.🤔 Checklist before submitting
🤖 Generated with Claude Code