-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Creating a release | ||
|
||
1. Review github issues, triage, close and merge issues related to the release. | ||
2. Update CHANGES.md, with date release, notes, and version. | ||
3. Pull down the repository locally on the master branch. | ||
4. Ensure there are no outstanding commits and the branch is clean. | ||
5. Run `npm install` and ensure all dependencies correctly install. | ||
6. Run `npm run test` and ensure testing and linting passes. | ||
7. Run `npm version vx.x.x -m "version x.x.x"` where `x.x.x` is the version. | ||
8. Run `git push upstream master --tags` | ||
9. Run `npm publish` | ||
10. Go to the [Github release page][Releases] and hit 'Draft a new release'. | ||
11. Paste the Changelog content for this release and add additional release notes. | ||
12. Choose the tag version and a title matching the release and publish. | ||
13. Notify core maintainers of the release via email. | ||
|
||
[Releases]: https://github.com/senecajs/seneca-web-adapter-connect/releases |