Add article: Node.js release schedule and version number changes#37
Merged
Conversation
Add a new blog article explaining the 2026 Node.js release schedule change: one major a year, year-based version numbers, every release becoming LTS, and the new Alpha channel. Includes a custom SVG timeline matching the existing release-schedule diagram style. Add update notes to the checking-node-js-version, installing-node-js, and whats-new-in-nodejs-26 articles, whose odd/even explanations are now superseded, and lightly correct the affected sentences. Update the content calendar with the new article, internal linking map, and notes. https://claude.ai/code/session_01Vecdu4nTcdKdqYBTTKJcdy
Remove the custom release-schedule SVG and reword the lifecycle section to read naturally without it (the schedule table already shows the cadence). Add a light aside on version numbers matching the year, and remove the PR preview screenshot from the repo. https://claude.ai/code/session_01Vecdu4nTcdKdqYBTTKJcdy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New blog article explaining the 2026 change to the Node.js release schedule and version numbering: one major a year, year-based version numbers, every release becoming LTS, and the new Alpha channel. Based on the official "Evolving the Node.js Release Schedule" announcement and InfoQ's coverage.
It follows the established house style (intro + TL;DR → Quick Answer → "how it works today" refresher → the four changes → new lifecycle → v26 vs v27 → forward schedule → why → "what it means for you" → FAQ → CTA), with Luciano's personal voice woven throughout (the odd-release admission, the teacher's confession, the year-math/Ubuntu analogy plus a light "stars lining up" aside on version numbers matching the year, a substantive maintainer-gratitude passage, and a library-author commitment to wire Alpha into CI).
Changes
New content
src/content/blog/nodejs-release-schedule-changes/index.md— the article (slugnodejs-release-schedule-changes, full FAQ schema block). Schedule details are conveyed via markdown tables (lifecycle, v26 vs v27, and the forward schedule).Update notes (the odd/even explanations are now superseded — each gets a
:::notepointing to the new article plus a light "through Node.js 26" correction):src/content/blog/checking-node-js-version/index.mdsrc/content/blog/installing-node-js/index.mdsrc/content/blog/whats-new-in-nodejs-26/index.md(framed as "v26 is the last release of the old model")Strategy
.claude/content-calendar.md— added the article to Existing Content, mapped its internal links both ways, and noted that release "what's new" posts are now yearly and that release-policy news is a distinct evergreen hook.Verification
pnpm buildpasses (14 pages).https://claude.ai/code/session_01Vecdu4nTcdKdqYBTTKJcdy