From fe29dfa89c7f9d2b44ca8bcbf4ad6694c8a848fb Mon Sep 17 00:00:00 2001 From: Steve Gravrock Date: Sat, 21 May 2022 09:42:26 -0700 Subject: [PATCH] Update release process instructions * 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 --- RELEASE.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 47f32104..00c5838e 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -36,9 +36,10 @@ When ready to release - specs are all green and the stories are done: ### Commit and push core changes 1. Run the browser tests using `scripts/run-all-browsers`. -1. Commit release notes and version changes (jasmine.js, package.json) -1. Push -1. Wait for Circle CI to go green +2. Commit release notes and version changes (jasmine.js, package.json) +3. Push +4. Tag the release and push the tag. +5. Wait for Circle CI to go green ### 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 -1. Run the tests on Windows. (CI only tests on Linux.) 1. `npm adduser` to save your credentials locally 1. `npm publish .` to publish what's in `package.json`