Skip to content

Conversation

@stuartmorgan-g
Copy link
Contributor

See flutter/flutter#129633 for context.

Since flutter/packages doesn't pin, this test is somewhat prone to out-of-band failures when transitive dependencies are published. Using the --downgrade flag uses the oldest possible versions of dependencies rather than the newest, which avoids picking up newly published versions.

See flutter/flutter#129633 for context.

Since flutter/packages doesn't pin, this test is somewhat prone to out-of-band failures when transitive dependencies are published. Using the `--downgrade` flag uses the oldest possible versions of dependencies rather than the newest, which avoids picking up newly published versions.
@copybara-service
Copy link

Thank you for your contribution! This project uses Gerrit for code reviews. Your pull request has automatically been converted into a code review at:

https://dart-review.googlesource.com/c/sdk/+/314920

Please wait for a developer to review your code review at the above link; you can speed up the review if you sign into Gerrit and manually add a reviewer that has recently worked on the relevant code. See CONTRIBUTING.md to learn how to upload changes to Gerrit directly.

Additional commits pushed to this PR will update both the PR and the corresponding Gerrit CL. After the review is complete on the CL, your reviewer will merge the CL (automatically closing this PR).

@stuartmorgan-g stuartmorgan-g deleted the flutter-packages-analyze-downgrade branch July 19, 2023 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant