You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[vector_graphics] review package API and publish new versions. #157626
changed the title [-][vector_graphics] review package API and publish 1.0 versions[/-][+][vector_graphics] review package API and publish new versions.[/+]on Oct 25, 2024
Capturing from offline discussion to provide more context here: in the past, vector_graphics* has use exact, pinned dependencies between the different versions, and special release logic that ensures they are all published in dependency order. Both of these would require a bunch of custom work in our repo, and it sounds like we don't need that level of tight coupling any more.
For now I'm importing with almost-exactly-pinned versions (allowing both the last pre-import and the first post-import version, but nothing else) to preserve existing behavior, with comments referencing this issue in the pubspec, but very soon we should replace those contraints with something based on the plan going forward. My strong preference would be to apply semver, as even setting aside the tooling aspects, having a small number of packages in a repo with many, many other packages that follows weird special rules that anyone touching the package has to know about is a significant maintenance burden.
flutter/packages#7991 changed the version of only one package, so things are now mis-aligned. If the solution doesn't end up being to use semver, that will need to be addressed.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
stuartmorgan-g commentedon Oct 25, 2024
That will be tricky since they are all on
1.1.11+1:)jonahwilliams commentedon Oct 25, 2024
well, something like that :)
1.5!
[-][vector_graphics] review package API and publish 1.0 versions[/-][+][vector_graphics] review package API and publish new versions.[/+]stuartmorgan-g commentedon Oct 28, 2024
Capturing from offline discussion to provide more context here: in the past,
vector_graphics*has use exact, pinned dependencies between the different versions, and special release logic that ensures they are all published in dependency order. Both of these would require a bunch of custom work in our repo, and it sounds like we don't need that level of tight coupling any more.For now I'm importing with almost-exactly-pinned versions (allowing both the last pre-import and the first post-import version, but nothing else) to preserve existing behavior, with comments referencing this issue in the pubspec, but very soon we should replace those contraints with something based on the plan going forward. My strong preference would be to apply semver, as even setting aside the tooling aspects, having a small number of packages in a repo with many, many other packages that follows weird special rules that anyone touching the package has to know about is a significant maintenance burden.
stuartmorgan-g commentedon Nov 1, 2024
flutter/packages#7991 changed the version of only one package, so things are now mis-aligned. If the solution doesn't end up being to use semver, that will need to be addressed.
[vector_graphics*] Relax dependency constraints of vector_graphics, v…
github-actions commentedon Nov 19, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.[vector_graphics*] Relax dependency constraints of vector_graphics, v…
[vector_graphics*] Relax dependency constraints of vector_graphics, v…