fix: Fixing CI on flutter 3.35#1339
Merged
Merged
Conversation
marcossevilla
previously approved these changes
Aug 18, 2025
Member
|
@erickzanardo should we add an extra step for the completion as it's failing at some workflows? |
Member
Author
hm, is the code completion failing? Can you point me to that failure? |
marcossevilla
approved these changes
Aug 18, 2025
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
2 participants
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.
Status
READY
Description
With the recent release of Flutter 3.35 our CI started to fail since now, when creating a dart project with the dart version that comes bundled with that version, the
pathversion is now by default added to the pubspec.That was breaking the check license e2e test, since it expected only MIT license dependencies and the path one is a BSD-3-Clause.
Type of Change