Update platform version for 261#8773
Merged
Merged
Conversation
Collaborator
|
Great points. Let's walk through them in person! |
pq
approved these changes
Feb 25, 2026
Member
Author
|
Update to initial comments: I think the compatibility problems are okay, as they reflect Dart plugin not yet being available for 2026.1 also. We will release updated Dart plugin before Flutter this time (last release this was harder because the new Dart version broke old Flutter versions) |
helin24
added
the
autosubmit
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.
A problem is that I may need a way for users to download a dev Dart plugin as well.
Another problem is there are many new verify issues for 2026.1 (these can be seen on the jetbrains site already, even though our current plugins aren't technically compatible with 2026.1). Maybe it would make sense to focus on fixing those first, and make this an issue instead so we know that compatibility for 2026.1 is on our agenda.