From c14bfe3e5fe5f4e78482ab8de3a302fb9ddf7f33 Mon Sep 17 00:00:00 2001 From: Steve Gravrock Date: Sat, 3 Sep 2022 11:02:13 -0700 Subject: [PATCH] Updated release process doc * Fixed description of patch releases * Moved -npm release docmentation to that repo * Refer to -npm specifically rather than "binding libraries" generally, now that we only have one of those that versions in lockstep with core. --- RELEASE.md | 28 ++++++++++------------------ 1 file changed, 10 insertions(+), 18 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 347c6b3a..517752c2 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -18,12 +18,11 @@ copied to `jasmine.js` when the distribution is built. When releasing a new version, update `package.json` with the new version and `npm run build` to update the gem version number. -Note that Jasmine should only use the "patch" version number in the following cases: +Note that Jasmine should only use the "patch" version number if the new release +contains only bug fixes. -* Changes related to packaging for a specific binding library (npm or browser-runner) -* Fixes for regressions. - -When jasmine-core revs its major or minor version, the binding libraries should also rev to that version. +When `jasmine-core` revs its major or minor version, the `jasmine` NPM package +should also rev to that version. ## Release @@ -61,20 +60,13 @@ for instructions. 1. `rake release[${version}]` to copy the current edge docs to the new version 1. Commit and push. -### Release the binding libraries +### Release the `jasmine` NPM package -#### NPM +See . -1. Create release notes using Anchorman as above -1. In `package.json`, update both the package version and the jasmine-core dependency version -1. Commit and push. -1. Wait for Circle CI to go green again. -1. `grunt release `. (Note: This will publish the package by running `npm publish`.) +### Publish the GitHub release -### Finally - -For each of the above GitHub repos: 1. Visit the releases page and find the tag just published. -1. Paste in a link to the correct release notes for this release. The link should reference the blob and tag correctly, and the markdown file for the notes. -1. If it is a pre-release, mark it as such. -1. For core, attach the standalone zipfile. +2. Paste in a link to the correct release notes for this release. +3. If it is a pre-release, mark it as such. +4. Attach the standalone zipfile.