Skip to content

fix: Node.js references in release posts #7998

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

Merged
merged 1 commit into from
Jul 22, 2025

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Jul 20, 2025

Our guidelines indicates we should be using Node.js instead of Node.

Refs: https://github.com/nodejs/node/blob/668e52339261ec21c7388884620987914c833395/doc/README.md#L213-L216

Description

Validation

Related Issues

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run pnpm format to ensure the code follows the style guide.
  • I have run pnpm test to check if all tests are passing.
  • I have run pnpm build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

@Copilot Copilot AI review requested due to automatic review settings July 20, 2025 09:04
@aduh95 aduh95 requested review from a team as code owners July 20, 2025 09:04
Copy link

vercel bot commented Jul 20, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Jul 20, 2025 9:05am

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This pull request standardizes Node.js naming conventions by updating release post titles from "Node" to "Node.js" according to official Node.js style guidelines. The changes affect hundreds of release announcement files spanning from v0.4.4 through v14.17.3.

  • Updates all release post titles to use the consistent "Node.js" naming format
  • Maintains consistent branding across historical release announcements
  • Aligns with Node.js project style guidelines for proper project name usage

Reviewed Changes

Copilot reviewed 300 out of 715 changed files in this pull request and generated no comments.

Show a summary per file
File Description
v14.x release files Updated 13 Node.js v14 release post titles from "Node" to "Node.js"
v13.x release files Updated 21 Node.js v13 release post titles from "Node" to "Node.js"
v12.x release files Updated 47 Node.js v12 release post titles from "Node" to "Node.js"
v11.x release files Updated 14 Node.js v11 release post titles from "Node" to "Node.js"
v10.x release files Updated 43 Node.js v10 release post titles from "Node" to "Node.js"
v0.x release files Updated 184+ legacy Node.js release post titles from "Node" or variants to "Node.js"

Copy link

codecov bot commented Jul 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.12%. Comparing base (edacebc) to head (1b815fb).
Report is 9 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7998      +/-   ##
==========================================
+ Coverage   73.09%   73.12%   +0.03%     
==========================================
  Files          95       95              
  Lines        8354     8354              
  Branches      219      218       -1     
==========================================
+ Hits         6106     6109       +3     
+ Misses       2247     2244       -3     
  Partials        1        1              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@AugustinMauroy AugustinMauroy left a comment

Choose a reason for hiding this comment

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

LGMT !

Copy link
Member

@RafaelGSS RafaelGSS left a comment

Choose a reason for hiding this comment

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

We should also update the release-post script, as all of them are automatically generated.

@AugustinMauroy
Copy link
Member

Antoine do it, he updated the template

@aduh95 aduh95 added the github_actions:pull-request Trigger Pull Request Checks label Jul 21, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jul 21, 2025
Copy link
Contributor

github-actions bot commented Jul 21, 2025

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 97 🟢 100 🟢 100 🔴 66 🔗
/en/about 🟢 100 🟢 97 🟢 100 🔴 58 🔗
/en/about/previous-releases 🟢 99 🟢 93 🟢 100 🔴 61 🔗
/en/download 🟢 98 🟢 100 🟢 100 🔴 66 🔗
/en/blog 🟢 100 🟢 100 🟢 96 🔴 69 🔗

@avivkeller avivkeller added this pull request to the merge queue Jul 22, 2025
Merged via the queue into nodejs:main with commit 16c6d1e Jul 22, 2025
15 checks passed
@aduh95 aduh95 deleted the fix-release-posts-title branch July 22, 2025 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants