Description

Our GCP Node SDK references the NodeJS releases page and as part of our CI, we check for broken links when generating documentation pages. With some recent changes, the link to nodejs.org/en/about/releases stopped working, which broke our CI pipeline.

Also, searching on Github, seems like multiple projects references the same page:

• https://github.com/search?q=%22https%3A%2F%2Fnodejs.org%2Fen%2Fabout%2Freleases%22&type=code (28k hits)

I've added the extra route in the next.rewrites.mjs file accordingly to PR #5580, which also reference the file https://github.com/nodejs/build/blob/f7e0f90a55b0c866041668e4285a16274f1e36f7/ansible/www-standalone/resources/config/nodejs.org?plain=1#L338. And we can see that /en/about/releases is indeed missing from the new rewrite logic.

Validation

Manual Testing that the Rewrites Work.

Related Issues

• A SDK release on hold due to that: chore(main): release 7.0.0 googleapis/nodejs-bigquery#1231
• We started a fix for our internal repository template, which will cause all of our Node repos to be updated: docs: fix node release schedule link googleapis/synthtool#1841

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npx turbo lint to ensure the code follows the style guide. And run npx turbo lint:fix to fix the style errors if necessary.
• I have run npx turbo format to ensure the code follows the style guide.
• I have run npx turbo test to check if all tests are passing, and/or npx turbo test:snapshot to update snapshots if I created and/or updated React Components.
• I've covered new added functionality with unit tests if necessary.