Repository navigation
chore: Bump flame_svg to 2.0.0 on main after the hotfix release - #4029
Merged
Merged
Conversation
spydon
enabled auto-merge (squash)
August 30, 2026 16:40
2 of 3 tasks
spydon
added a commit
that referenced
this pull request
Oct 3, 2026
…4089) # Description Users on the stable flame 1.38 line who upgrade to Flutter 3.47 could not build with `flame_3d` 0.3.0, because its flutter_gpu backend predates the API changes that #3995 adapted to, and the only published version with that fix, 0.4.0-dev.0, requires flame 2.0.0-dev.0. The fix for them is the `flame_3d` 0.3.1 and 0.3.2 hotfix releases cut from the `flame-v1.38.2` tag, which already contains the #3995 adaptation, on the branch `hotfix/flame_3d-v0.3.1`. 0.3.1 raised the `flutter` constraint to `>=3.47.0`, but the melos bootstrap step on CI synced the shared bootstrap environment back into the package before publishing, so it went out with `>=3.41.0`. 0.3.2 removes that sync on the hotfix branch and is published with the intended constraint. 0.3.1 should be retracted on pub.dev so that Flutter 3.41 to 3.46 users do not resolve it. This PR is the forward port of those releases to `main`, following the same approach as #4029 for flame_svg: it adds the 0.3.1 and 0.3.2 changelog entries so the history on `main` stays complete. The `flame_3d` version on `main` is already 0.4.0-dev.0, so no version bump is needed here. ## Checklist - [x] I have followed the [Contributor Guide] when preparing my PR. - [-] I have updated/added tests for ALL new/updated/fixed functionality. - [-] I have updated/added relevant documentation in `docs` and added dartdoc comments with `///`. - [-] I have updated/added relevant examples in `examples` or `docs`. ## Breaking Change? - [ ] Yes, this PR is a breaking change. - [x] No, this PR is not a breaking change. [Contributor Guide]: https://github.com/flame-engine/flame/blob/main/CONTRIBUTING.md
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
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.
Description
flame_svg 2.0.0 was published from the
hotfix/flame_svg-v2.0.0branch (based onflame-v1.38.2, containing #3956 and #3969) so it could be released without a new flame release. This ports the version bump, the changelog entries, and the^2.0.0constraint bumps forexamplesand the flame_svg example back tomain, so the nextmelos versiononmaincomputes a version above the one already on pub.dev.The flame_svg 1.13.0 entry is kept since it was already recorded here, so the 2.0.0 entry only lists the commits not already covered by it.
Checklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?
Related Issues
Follow-up to the flame_svg-v2.0.0 release: https://github.com/flame-engine/flame/releases/tag/flame_svg-v2.0.0