admin/jasmine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated release process doc

Browse Source 
* 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.
This commit is contained in:
Steve Gravrock
2022-09-03 11:02:13 -07:00
parent 26c48ab324
commit c14bfe3e5f
1 changed files with 10 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
RELEASE.md
View File

@@ -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 version, update `package.json` with the new version and `npm run build` to
update the gem version number. 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) When `jasmine-core` revs its major or minor version, the `jasmine` NPM package
* Fixes for regressions. should also rev to that version.
When jasmine-core revs its major or minor version, the binding libraries should also rev to that version.
## Release ## Release
@@ -61,20 +60,13 @@ for instructions.
1. `rake release[${version}]` to copy the current edge docs to the new version 1. `rake release[${version}]` to copy the current edge docs to the new version
1. Commit and push. 1. Commit and push.
### Release the binding libraries ### Release the `jasmine` NPM package
#### NPM See <https://github.com/jasmine/jasmine-npm/blob/main/RELEASE.md>.
1. Create release notes using Anchorman as above ### Publish the GitHub release
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`.)
### Finally
For each of the above GitHub repos:
1. Visit the releases page and find the tag just published. 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. 2. Paste in a link to the correct release notes for this release.
1. If it is a pre-release, mark it as such. 3. If it is a pre-release, mark it as such.
1. For core, attach the standalone zipfile. 4. Attach the standalone zipfile.