From bd7d630297a0b32e82b3a5c2ce552b719ddc1458 Mon Sep 17 00:00:00 2001 From: alancleary Date: Thu, 9 Nov 2023 09:32:19 -0700 Subject: [PATCH] Updated release checklist. Added test building the NPM package and fixed a typo. --- .github/ISSUE_TEMPLATE/release-checklist.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release-checklist.md b/.github/ISSUE_TEMPLATE/release-checklist.md index 0e80c12..36bb485 100644 --- a/.github/ISSUE_TEMPLATE/release-checklist.md +++ b/.github/ISSUE_TEMPLATE/release-checklist.md @@ -8,8 +8,9 @@ assignees: '' --- - [ ] Create a branch for the release. -- [ ] Update the dependencies. The dependabot PR backlog is not comprehensive and doesn't include transitive dependencies, and merging them one at a time tends to break things, so the best way to do this is manually with npm. -- [ ] Bump the `"version"` number in `package.json` and reinstall the dependencies so the correct version number is in `package.lock.json`. +- [ ] Update the dependencies. The dependabot PR backlog is not comprehensive and doesn't include transitive dependencies, and merging them one at a time tends to break things, so the best way to do this is manually with `npm`. +- [ ] Do a test build of the NPM package on your local machine so you know if something is going off the rails before the automated build action on GitHub. +- [ ] Bump the `"version"` number in `package.json` and reinstall the dependencies so the correct version number is in `package-lock.json`. - [ ] Open a PR that merges the release branch into main. - [ ] Merge the release PR after it passes testing and review. - [ ] Tag a corresponding release on GitHub. This will trigger an automated NPM package build on GitHub. If the package build succeeds it will be automatically published to NPM.