Analyze and test with both lowest and highest supported Flutter SDK versions in CI #235
Conversation
This file contains 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
fujidaiti
changed the title
fujidaiti
force-pushed
the
double-sdk-version-test
branch
from
b35253c to
32fd21e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related issues (optional)
Closes #229.
Description
The workflow file was updated to run unit tests and static analysis for both the lowest and highest supported Flutter SDK versions. This approach helps detect potential compatibility issues across the entire supported SDK range. For example, issue #144 stemmed from accidentally using newly added APIs in Flutter 3.22 that don't exist in lower versions, while issue #233 arose due to a breaking change introduced in Flutter 3.24.
Summary (check all that apply)