Skip to content

2026-04-21, Version 26.0.0 (Current)#62526

Open
RafaelGSS wants to merge 1 commit intomainfrom
v26.0.0-proposal
Open

2026-04-21, Version 26.0.0 (Current)#62526
RafaelGSS wants to merge 1 commit intomainfrom
v26.0.0-proposal

Conversation

@RafaelGSS
Copy link
Copy Markdown
Member

PR-URL: TBD

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/crypto
  • @nodejs/http
  • @nodejs/loaders
  • @nodejs/net
  • @nodejs/typescript
  • @nodejs/userland-migrations

@RafaelGSS RafaelGSS added release Issues and PRs related to Node.js releases. v26.x Issues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch. labels Mar 31, 2026
@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Mar 31, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 31, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.71%. Comparing base (cd391b5) to head (df1f8fb).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #62526      +/-   ##
==========================================
- Coverage   89.71%   89.71%   -0.01%     
==========================================
  Files         694      694              
  Lines      214245   214430     +185     
  Branches    41119    41146      +27     
==========================================
+ Hits       192211   192369     +158     
- Misses      14109    14116       +7     
- Partials     7925     7945      +20     

see 32 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Member

@targos targos left a comment

Choose a reason for hiding this comment

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

Blocking on V8 update (#61898) and #62533 (or some variation of it).

@MikeMcC399
Copy link
Copy Markdown
Contributor

https://github.com/nodejs/Release/blob/main/schedule.json shows:

  "v26": {
    "start": "2026-04-22",
    "lts": "2026-10-28",
    "maintenance": "2027-10-20",
    "end": "2029-04-30",
    "codename": ""
  }

The date "start": "2026-04-22" is not the same as in the title of this PR
"2026-04-21, Version 26.0.0 (Current)"

Is that correct or does one of the dates need changing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

meta Issues and PRs related to the general management of the project. release Issues and PRs related to Node.js releases. v26.x Issues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants