Skip to content

doc: add r2 cloudflare instruction on release #50623

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

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions doc/contributing/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -1018,6 +1018,19 @@ This script will use the promoted builds and changelog to generate the post. Run
"Set as the latest release".
* Click on the "Publish release" button.

#### (Temporary) Update the Cloudflare R2 Worker Symlinks

We have adopted Cloudflare R2 and Cloudflare Workers for our
Release Assets (see <https://github.com/nodejs/build/issues/3461>).

For now, after a release is done, the symlinks need to be updated manually.
This can be done by simply
[triggering this GitHub Worfklow](https://github.com/nodejs/release-cloudflare-worker/actions/workflows/update-links.yml).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[triggering this GitHub Worfklow](https://github.com/nodejs/release-cloudflare-worker/actions/workflows/update-links.yml).
[triggering this GitHub Worfklow](https://github.com/nodejs/release-cloudflare-worker/actions/workflows/update-links.yml), and then [deploying](https://github.com/nodejs/release-cloudflare-worker/actions/workflows/deploy.yml) the update

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the manual deployment really needed? Doesn't the sync already deploy it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can add that to the sync workflow, but it currently only opens a PR


This workflow should then update the R2 symlinks to match the latest releases.

**Note:** This is a temporary workaround as we automate this process.

### 19. Announce

The nodejs.org website will automatically rebuild and include the new version.
Expand Down