-
Notifications
You must be signed in to change notification settings - Fork 2
Milestone
Description
This issue is for tracking changes for the 1.0.0 release.
Release steps
- Branch: Starting from
develop, cut a release branch namedrelease/1.0.0for your changes. - Version bump: Bump the version number in
package.json,package-lock.json,src/cli.tsand any other relevant files if it does not already reflect the version being released. - Changelog: Add/update the changelog in
CHANGELOG.md. - Props: update
CREDITS.mdfile with any new contributors, confirm maintainers are accurate. - New files: Check to be sure any new files/paths that are unnecessary in the production version are included in
.gitattributes. - Readme updates: Make any other readme changes as necessary.
- Merge: Make a non-fast-forward merge from your release branch to
develop(or merge the pull request), then do the same fordevelopintotrunk(git checkout trunk && git merge --no-ff develop).trunkcontains the stable development version. - Push: Push your
trunkbranch to GitHub (e.g.git push origin trunk). - Release: Create a new release, naming the tag and the release with the new version number, and targeting the
trunkbranch. Paste the changelog fromCHANGELOG.mdinto the body of the release and include a link to the closed issues on the milestone. - Close milestone: Edit the milestone with release date (in the
Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone. - Punt incomplete items: If any open issues or PRs which were milestoned for
1.0.0do not make it into the release, update their milestone to1.0.1orFuture Release.
Metadata
Metadata
Assignees
Labels
No labels
Projects
Status
Done