Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Mar 17, 2022
5 changes: 4 additions & 1 deletion .github/workflows/ci.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -197,9 +197,12 @@ jobs:
with:
fetch-depth: 0

- uses: actions/download-artifact@v3
- name: Download artifact
uses: dawidd6/action-download-artifact@v2
id: download
with:
branch: release
workflow_conclusion: completed
name: "npm-package"
path: release-npm-package

Expand Down
2 changes: 1 addition & 1 deletion docs/MAINTAINING.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 `release` (the npm workflow will look for this when a new GitHub release is published)
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
Expand Down