Commit 2feb078
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -282,7 +282,15 @@ You can integrate the PRs into the proposal without running full CI. | |||
| 282 | 282 | ||
| 283 | 283 | ### 2. Create a new branch for the release | |
| 284 | 284 | ||
| 285 | - ⚠️ At this point, you can either run `git node release --prepare`: | ||
| 285 | + > \[!TIP] Once the staging branch is up-to-date you can use the | ||
| 286 | + > [`create-release-proposal`][] action to generate the proposal. | ||
| 287 | + | ||
| 288 | + ```bash | ||
| 289 | + gh workflow run "Create Release Proposal" -f release-line=N -f release-date=YYYY-MM-DD | ||
| 290 | + ``` | ||
| 291 | + | ||
| 292 | + If you prefer to run it locally you can either run | ||
| 293 | + `git node release --prepare`: | ||
| 286 | 294 | ||
| 287 | 295 | ```bash | |
| 288 | 296 | git node release -S --prepare x.y.z | |
@@ -1424,6 +1432,7 @@ Typical resolution: sign the release again. | |||
| 1424 | 1432 | [Node.js Snap management repository]: https://github.com/nodejs/snap | |
| 1425 | 1433 | [Partner Communities]: https://github.com/nodejs/community-committee/blob/HEAD/governance/PARTNER_COMMUNITIES.md | |
| 1426 | 1434 | [Snap]: https://snapcraft.io/node | |
| 1435 | + [`create-release-proposal`]: https://github.com/nodejs/node/actions/workflows/create-release-proposal.yml | ||
| 1427 | 1436 | [build-infra team]: https://github.com/orgs/nodejs/teams/build-infra | |
| 1428 | 1437 | [expected assets]: https://github.com/nodejs/build/tree/HEAD/ansible/www-standalone/tools/promote/expected_assets | |
| 1429 | 1438 | [nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post/index.mjs | |
0 commit comments