From f4b6e64b6bb0800e691a4163716c4bf7399ef9f0 Mon Sep 17 00:00:00 2001 From: RafaelGSS Date: Mon, 25 Nov 2024 12:33:44 -0300 Subject: [PATCH 1/2] doc: add create-release-action to process --- doc/contributing/releases.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index 3ae682169873df..c7a680bf7251fd 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -282,7 +282,13 @@ 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. + +![screenshot running action via github ui](https://github.com/user-attachments/assets/244795d0-3753-45ea-a259-169d15c40239) + +If you prefer to run it locally you can either run +`git node release --prepare`: ```bash git node release -S --prepare x.y.z @@ -1388,6 +1394,7 @@ take place once a new LTS line has been released. [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 From 115e5d5d6e748f762256ee1587a4d52788e439ae Mon Sep 17 00:00:00 2001 From: RafaelGSS Date: Wed, 27 Nov 2024 17:52:39 -0300 Subject: [PATCH 2/2] fixup! doc: add create-release-action to process --- doc/contributing/releases.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index c7a680bf7251fd..a49fa980f7e068 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -285,7 +285,9 @@ You can integrate the PRs into the proposal without running full CI. > \[!TIP] Once the staging branch is up-to-date you can use the > [`create-release-proposal`][] action to generate the proposal. -![screenshot running action via github ui](https://github.com/user-attachments/assets/244795d0-3753-45ea-a259-169d15c40239) +```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`: