Cease pinning CI Flutter to minor version number #20
Conversation
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
Instead, the CI will now upgrade Flutter to latest stable version (as long as it’s 3.x). This is a better trade-off for a sample repo. We don’t need to update several lines in 3 separate YAML files every 3 months. Since this is a small sample repo, it is very unlikely that a minor stable release will break anything.
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.
Instead, the CI will now upgrade Flutter to latest stable version (as long as it’s 3.x). This is a better trade-off for a sample repo. We don’t need to update several lines in 3 separate YAML files every 3 months. Since this is a small sample repo, it is very unlikely that a minor stable release will break anything.