Skip to content

Add a table about SDK support in README #8288

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

Merged
merged 1 commit into from
Jun 26, 2025
Merged

Conversation

helin24
Copy link
Member

@helin24 helin24 commented Jun 26, 2025

This links to the flutter.dev site and provides a table similar to what Danny added: https://dartcode.org/sdk-version-compatibility/

@helin24 helin24 requested review from pq and jwren June 26, 2025 16:52
Copy link
Contributor

@pq pq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I LOVE this!

Thinking ahead, I wonder if we couldn't codegen the table? Is there somewhere else the compatibility info is captured that we can pull from?

(My concern is the table getting stale or out of sync.)

@helin24
Copy link
Member Author

helin24 commented Jun 26, 2025

Yes, some sort of codegen would be nice, ideally run each time we release. I think we would want to move the version we want to warn users on and the oldest supported version to a configuration file

@helin24 helin24 merged commit bc8fc55 into flutter:master Jun 26, 2025
7 of 8 checks passed
@helin24 helin24 deleted the readme-sdk branch June 26, 2025 17:03
@pq
Copy link
Contributor

pq commented Jun 26, 2025

Yes, some sort of codegen would be nice, ideally run each time we release. I think we would want to move the version we want to warn users on and the oldest supported version to a configuration file

Good idea! Maybe open an issue to keep track of the idea?

@helin24
Copy link
Member Author

helin24 commented Jun 26, 2025

Already done :) #8289

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.

3 participants