-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci/various] Update for 3.19 stable #6147
Conversation
@@ -295,21 +295,21 @@ targets: | |||
timeout: 30 | |||
properties: | |||
target_file: analyze_legacy.yaml | |||
channel: "3.13.9" | |||
channel: "3.16.9" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does most of this pr update to 3.13 but the legacy test updates to 3.16? Is the legacy test by definition only one flutter release old?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does most of this pr update to 3.13 but the legacy test updates to 3.16? Is the legacy test by definition only one flutter release old?
There are two legacy tests: N-1, and N-2. This is the N-1 test, which is by definition one release old, and the one just below is N-2, which is by definition two releases old.
(We have both main because if a package decides to drop N-2 but still support N-1, we want to make sure it doesn't accidentally uses APIs from N, but it won't be able to run the N-2 tests.)
@@ -19,7 +19,7 @@ tasks: | |||
script: .ci/scripts/tool_runner.sh | |||
args: | |||
- "pubspec-check" | |||
- "--min-min-flutter-version=3.10.0" | |||
- "--min-min-flutter-version=3.13.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nonblocking? Why not make this the highest patch version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is covered in the wiki page about doing stable updates:
We generally use .0 here, not the latest hotfix, under the assumption that there are not going to be analysis-breaking changes in a hotfix.
In practice, we've never had a case of this being a problem since we set up the legacy tests, and it means compatibility for more users on old versions.
Thanks for bumping this! |
0af905d [flutter_migrate] Implement lineTerminator in the MemoryStdout fake (flutter/packages#6152) f865baf Raise gradle wrapper version of legacy project (flutter/packages#6132) b4d8ad7 Bump github/codeql-action from 3.24.1 to 3.24.3 (flutter/packages#6142) cc34b78 [ci/various] Update for 3.19 stable (flutter/packages#6147) 10a8b76 Roll Flutter (stable) from 4145645 to bae5e49 (1550 revisions) (flutter/packages#6145) a36071b Roll Flutter from a628814 to d7867ca (66 revisions) (flutter/packages#6146)
0af905d [flutter_migrate] Implement lineTerminator in the MemoryStdout fake (flutter/packages#6152) f865baf Raise gradle wrapper version of legacy project (flutter/packages#6132) b4d8ad7 Bump github/codeql-action from 3.24.1 to 3.24.3 (flutter/packages#6142) cc34b78 [ci/various] Update for 3.19 stable (flutter/packages#6147) 10a8b76 Roll Flutter (stable) from 4145645 to bae5e49 (1550 revisions) (flutter/packages#6145) a36071b Roll Flutter from a628814 to d7867ca (66 revisions) (flutter/packages#6146)
Does the steps from https://github.com/flutter/flutter/wiki/Updating-Packages-repo-for-a-stable-release to account for stable now being 3.19, and N-2 (and thus our minimum supported min version) being 3.13. These changes are version-bump-exempt [by repo policy](https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#version).
Does the steps from https://github.com/flutter/flutter/wiki/Updating-Packages-repo-for-a-stable-release to account for stable now being 3.19, and N-2 (and thus our minimum supported min version) being 3.13.
These changes are version-bump-exempt by repo policy.