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

Update release process instructions

Browse Source 
* Need to tag the release manually since the Ruby tooling for that was
  removed
* Windows CI works again, so no need to manually test on Windows
This commit is contained in:
Steve Gravrock
2022-05-21 09:42:26 -07:00
parent 41f7fabe2f
commit fe29dfa89c
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
RELEASE.md
View File

@@ -36,9 +36,10 @@ When ready to release - specs are all green and the stories are done:
### Commit and push core changes ### Commit and push core changes
1. Run the browser tests using `scripts/run-all-browsers`. 1. Run the browser tests using `scripts/run-all-browsers`.
1. Commit release notes and version changes (jasmine.js, package.json) 2. Commit release notes and version changes (jasmine.js, package.json)
1. Push 3. Push
1. Wait for Circle CI to go green 4. Tag the release and push the tag.
5. Wait for Circle CI to go green
### Build standalone distribution ### Build standalone distribution
@@ -47,7 +48,6 @@ When ready to release - specs are all green and the stories are done:
### Release the core NPM module ### Release the core NPM module
1. Run the tests on Windows. (CI only tests on Linux.)
1. `npm adduser` to save your credentials locally 1. `npm adduser` to save your credentials locally
1. `npm publish .` to publish what's in `package.json` 1. `npm publish .` to publish what's in `package.json`