Skip to content

Flutter doesn't follow semantic versioning #12108

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ueman
Copy link
Contributor

@ueman ueman commented Jun 8, 2025

Description of what this PR is changing or adding, and why:

Change the note that Flutter follow semantic versioning, since Flutter doesn't follow semantic versioning.

See here

Issues fixed by this PR (if any):

PRs or commits this PR depends on (if any):

Presubmit checklist

  • This PR is marked as draft with an explanation if not meant to land until a future stable release.
  • This PR doesn’t contain automatically generated corrections (Grammarly or similar).
  • This PR follows the Google Developer Documentation Style Guidelines — for example, it doesn’t use i.e. or e.g., and it avoids I and we (first person).
  • This PR uses semantic line breaks of 80 characters or fewer.

@ueman ueman requested review from sfshaza2, antfitch, parlough and a team as code owners June 8, 2025 08:35
@mit-mit
Copy link
Member

mit-mit commented Jun 11, 2025

Interesting, that line of text must have made it over when we clone the similar Dart text.

@@ -35,8 +35,7 @@ The following information is available for each Flutter release in the
SDK archive:

* **Flutter version**: The version number of the Flutter SDK
(for example, 3.0.0, 2.10.5). This follows semantic versioning, indicating
the significance of changes between releases.
(for example, 3.0.0, 2.10.5). Flutter doesn't follow semantic versioning.
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure. Is there any preference how to link to the document? Permalink, non-permalink?

Copy link
Contributor

@sfshaza2 sfshaza2 Jun 12, 2025

Choose a reason for hiding this comment

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

A permanent link, @ueman. The actual link would be:

{{site.github}}/flutter/flutter/blob/main/docs/releases/Release-versioning.md

(In general, we use "main" links instead of "master".)

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