1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: add create-release-action to process

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/55993
Reviewed-By: Ruy Adorno <ruy@vlt.sh>
This commit is contained in:
Rafael Gonzaga 2024-12-03 10:22:48 -03:00 committed by GitHub
parent 20bcaa081b
commit 742ea1c85f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/contributing/releases.md
View File

@ -282,7 +282,15 @@ You can integrate the PRs into the proposal without running full CI.
### 2. Create a new branch for the release
⚠️ At this point, you can either run `git node release --prepare`:
> \[!TIP] Once the staging branch is up-to-date you can use the
> [`create-release-proposal`][] action to generate the proposal.
```bash
gh workflow run "Create Release Proposal" -f release-line=N -f release-date=YYYY-MM-DD
```
If you prefer to run it locally you can either run
`git node release --prepare`:
```bash
git node release -S --prepare x.y.z
@ -1424,6 +1432,7 @@ Typical resolution: sign the release again.
[Node.js Snap management repository]: https://github.com/nodejs/snap
[Partner Communities]: https://github.com/nodejs/community-committee/blob/HEAD/governance/PARTNER_COMMUNITIES.md
[Snap]: https://snapcraft.io/node
[`create-release-proposal`]: https://github.com/nodejs/node/actions/workflows/create-release-proposal.yml
[build-infra team]: https://github.com/orgs/nodejs/teams/build-infra
[expected assets]: https://github.com/nodejs/build/tree/HEAD/ansible/www-standalone/tools/promote/expected_assets
[nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post/index.mjs