This template guides us through the steps of creating a new release, based on conversation and testing in #1692.
Discuss with @publiclab/is-maintainers if anything is ambiguous!
Also see:
Now, move to stable branch:
Draft a release:
Noting we're now in this process in #1751 for v3.7.0.
Release notes
Compile and edit release notes below, to be copied into the release description.
Added
Fixed
(almost ready):
Changed
This template guides us through the steps of creating a new release, based on conversation and testing in #1692.
Discuss with @publiclab/is-maintainers if anything is ambiguous!
Also see:
Checklist and coordination for v0.0.0 major/minor/patch release(see semantic versioning)package.json(ex Bump to v3.6.0 for new npm release #1695)examples/sw.js(ex Bump lockfile and sw.js versions for v3.6.0 #1734)npm installto updatepackage-lock.json(from recent node version - 16 at time of writing, in GitPod should work)package-lock.jsonmainbranch (freeze merges tomainbranch until next step)Now, move to
stablebranch:maintostablestablebranch, compile/dist/files withgrunt build/dist/files withgit add -f /dist/*and commit them tostablebranchstablebranch tonpmwithnpm publish(logging in first as necessary)Draft a release:
v0.0.0) based onstableor choosestable/scripts/update-demo) (from within GitPod works well)Noting we're now in this process in #1751 for
v3.7.0.Release notes
Compile and edit release notes below, to be copied into the release description.
Added
Fixed
(almost ready):
|character in CLI #1634Changed