From 2364a62aec7b0cc4116d458130ddae67647c769d Mon Sep 17 00:00:00 2001 From: joeyklee Date: Thu, 3 Feb 2022 00:29:23 -0500 Subject: [PATCH 1/2] docs: updates docs with latest release process --- docs/styleguide/maintenance-notes.md | 24 +++++++++--------------- 1 file changed, 9 insertions(+), 15 deletions(-) diff --git a/docs/styleguide/maintenance-notes.md b/docs/styleguide/maintenance-notes.md index 99b934fd7..9a39a9cee 100644 --- a/docs/styleguide/maintenance-notes.md +++ b/docs/styleguide/maintenance-notes.md @@ -9,27 +9,21 @@ - SEMVER/minor - SEMVER/major -## Before tagging a release releasing: bump the package version -1. open a PR to bump the package version: e.g. `git checkout -b v0.8.12` -2. bump the package version number that matches the `SEMVER/patch | SEMVER/minor | SEMVER/major` - - e.g. `SEMVER/patch`: `0.8.11` would become -> `0.8.12` - - e.g. `SEMVER/minor`: `0.8.11` would become -> `0.9.00` - - e.g. `SEMVER/major`: `0.8.11` would become -> `1.0.0` -3. run `npm i` <--- this makes sure your bumped package version makes it into the `package-lock.json` -4. run `npm run update:readme` <----- captures the version bump in the readme -5. run `git add .` -6. run `git commit -m "chore: bumps package"` -7. push this to your feature branch. -8. make a PR and merge to `main` ## Once we merge the PR to `main`: + 1. simply go to the `releases` sidebar > Screen Shot 2022-01-21 at 12 58 26 PM 2. go to the latest draft and click the edit button Screen Shot 2022-01-21 at 12 58 31 PM -3. click: publish the release - - +3. click: publish the release -- this will trigger a github workflow that will: + * get the latest tag version + * update the package.json + * update the readme with the latest version (pulled from the package.json) + * run npm install + * add, commit, and push those changes to `main` + * build the library + * and publish to npm *** From bc59ae1db1b357aee44a1b3c1cfe481de0f4ea6e Mon Sep 17 00:00:00 2001 From: joeyklee Date: Mon, 7 Feb 2022 19:21:02 -0500 Subject: [PATCH 2/2] docs: updates notes with semver example --- docs/styleguide/maintenance-notes.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/styleguide/maintenance-notes.md b/docs/styleguide/maintenance-notes.md index 9a39a9cee..5d41c3caf 100644 --- a/docs/styleguide/maintenance-notes.md +++ b/docs/styleguide/maintenance-notes.md @@ -6,9 +6,13 @@ 1. make sure to tag it with one of the following in the PR: - SEMVER/patch + - e.g. `SEMVER/patch`: `0.8.11` would become -> `0.8.12` - SEMVER/minor + - e.g. `SEMVER/minor`: `0.8.11` would become -> `0.9.0` - SEMVER/major + - e.g. `SEMVER/major`: `0.8.11` would become -> `1.0.0` +NOTE: if you are unsure quite likely it will be a `SEMVER/patch` for "...when you make backwards compatible bug fixes.". You can learn more about [Semantic Versioning](https://semver.org/). ## Once we merge the PR to `main`: