chore: Forward port the flame_3d 0.3.1 and 0.3.2 changelog entries - #4089
Merged
Merged
Conversation
spydon
force-pushed
the
chore/flame-3d-0.3.1-forward-port
branch
from
October 2, 2026 14:41
0df6c88 to
819c759
Compare
spydon
marked this pull request as ready for review
October 2, 2026 15:11
erickzanardo
approved these changes
Oct 2, 2026
spydon
changed the title
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
3 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.
Description
Users on the stable flame 1.38 line who upgrade to Flutter 3.47 could not build with
flame_3d0.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_3d0.3.1 and 0.3.2 hotfix releases cut from theflame-v1.38.2tag, which already contains the #3995 adaptation, on the branchhotfix/flame_3d-v0.3.1. 0.3.1 raised theflutterconstraint 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 onmainstays complete. Theflame_3dversion onmainis already 0.4.0-dev.0, so no version bump is needed here.Checklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?