Release: 0.7.2 - #162
Merged
Merged
Conversation
github-actions
Bot
requested review from
peterwilsoncc
and removed request for
a team
September 2, 2026 02:52
peterwilsoncc
approved these changes
Sep 2, 2026
Contributor
|
Third time's a charm Available: |
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
1 participant
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.
develop, cut a release branch namedrelease/X.Y.Zfor your changes.package.jsonandpackage-lock.jsonif it does not already reflect the version being released.CHANGELOG.md.CREDITS.mdfile with any new contributors, confirm maintainers are accurate.README.md.develop(or merge the Pull Request), then mergedevelopintotrunk(git checkout develop && git pull origin develop && git checkout trunk && git pull origin trunk && git merge --no-ff develop).trunkcontains the stable development version.trunkbranch to GitHub (e.g.git push origin trunk).trunkbranch. Paste the changelog fromCHANGELOG.mdinto the body of the release and include a link to the closed issues on the milestone. The release should now appear under releases.Due date (optional)field) and link to GitHub release (in theDescription field), then close the milestone.X.Y.Zdo not make it into the release, update their milestone toX.Y.Z+1,X.Y+- [ ]0,X+- [ ]0.0orFuture Release.