Archived
1
0

fix(ci): correctly download npm/docker artifacts (#4995)

* fix(ci): correctly download npm artifact

* fixup! fix(ci): correctly download npm artifact

* docs: update MAINTAINING

* fixup! docs: update MAINTAINING

* fixup! Merge branch 'main' into 4949-chore-fix-npm-workflow

* chore: get ci to run

* refactor: use vVERSION branch name instead of release

* refactor: use new download artifact in docker workflow

* refactor: clean up release-github-assets script

* fixup: remove extra v

* fixup! fixup: remove extra v
This commit is contained in:
Joe Previte
2022-03-17 11:52:39 -07:00
committed by GitHub
parent a0561c7685
commit 5afb26fb60
7 changed files with 36 additions and 17 deletions

View File

@ -164,7 +164,7 @@ If you're the current release manager, follow these steps:
### Publishing a release
1. Create a release branch called `v0.0.0` but replace with new version
1. Create a new branch called `v0.0.0` (replace 0s with actual version aka v4.1.0)
1. Run `yarn release:prep` and type in the new version (e.g., `3.8.1`)
1. GitHub Actions will generate the `npm-package`, `release-packages` and
`release-images` artifacts. You do not have to wait for this step to complete