◐ Shell
clean mode source ↗

doc: add create-release-action to process · nodejs/node@2feb078

@@ -282,7 +282,15 @@ You can integrate the PRs into the proposal without running full CI.

282282283283

### 2. Create a new branch for the release

284284285-

⚠️ 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`:

286294287295

```bash

288296

git node release -S --prepare x.y.z

@@ -1424,6 +1432,7 @@ Typical resolution: sign the release again.

14241432

[Node.js Snap management repository]: https://github.com/nodejs/snap

14251433

[Partner Communities]: https://github.com/nodejs/community-committee/blob/HEAD/governance/PARTNER_COMMUNITIES.md

14261434

[Snap]: https://snapcraft.io/node

1435+

[`create-release-proposal`]: https://github.com/nodejs/node/actions/workflows/create-release-proposal.yml

14271436

[build-infra team]: https://github.com/orgs/nodejs/teams/build-infra

14281437

[expected assets]: https://github.com/nodejs/build/tree/HEAD/ansible/www-standalone/tools/promote/expected_assets

14291438

[nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post/index.mjs