chore(release): Release flame_forge2d 0.20.0 - #4010
Merged
Merged
Conversation
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
2 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
Releases
flame_forge2d0.20.0, scoped to only this package so that the pending unreleased changes inflameand the other packages stay unreleased.New version:
flame_forge2d0.19.3+7 -> 0.20.0Included changes:
The flame-side breaking changes that also touched this package's directory (#3968, #3961) only affected its tests and example, so they are intentionally left out of the changelog: they do not apply to flame_forge2d consumers until flame v2 is released.
The package keeps its
flame: ^1.38.0dependency, verified by resolving against the published flame 1.38.0 and forge2d 0.15.1 (dart analyzeclean, all 91 tests pass,flutter pub publish --dry-runpasses). Since melos refuses to version a package whose workspace dependency (flame) has pending changes outside the scope filter, the version bump, changelogs, and dependent constraint updates were applied manually in the same format melos generates.On merge, the
release-tagworkflow tagsflame_forge2d-v0.20.0and triggers the publish workflow for it.Checklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?
Related Issues