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/0.4.0
for your changes.package.json
andpackage-lock.json
if it does not already reflect the version being released.CHANGELOG.md
.CREDITS.md
file with any new contributors, confirm maintainers are accurate.README.md
.develop
(or merge the Pull Request), then mergedevelop
intotrunk
(git checkout develop && git pull origin develop && git checkout trunk && git pull origin trunk && git merge --no-ff develop
).trunk
contains the stable development version.trunk
branch to GitHub (e.g.git push origin trunk
).trunk
branch. Paste the changelog fromCHANGELOG.md
into 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.0.4.0
do not make it into the release, update their milestone to0.5.0
orFuture Release
.