Release plan – v26.x Current
Open
Nobody has claimed this yet.
Release-agenda
- Dominant language
- JavaScript
- Stars
- 4.4k
- Forks
- 675
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 1
Description
Draft schedule - all dates subject to change
| Version | Release Date | Releaser(s) |
|---|---|---|
| 26.0.0 | 2026-05-05 | @RafaelGSS |
| 26.1.0 | 2026-05-07 | @aduh95 |
| 26.2.0 | 2026-05-20 | @aduh95 |
| 26.3.0 | 2026-06-01 | @aduh95 |
| 26.3.1 (Security) | 2026-06-18 | @aduh95 |
| 26.4.0 | 2026-06-24 | @aduh95 |
| 26.5.0 | 2026-07-08 | @richardlau |
| 26.5.1 (Security) | 2026-07-29 | @RafaelGSS |
| 26.6.0 | 2026-08-03 | @aduh95 |
| 26.7.0 | 2026-08-05 | @aduh95 |
| 26.8.0 | 2026-08-26 | @aduh95 |
| 26.8.1 | 2026-08-26 | @aduh95 |
| 26.x.x | 2026-09-09 | |
| 26.x.x | 2026-09-23 | |
| 26.x.x | 2026-10-07 | |
| 26.x.x | 2026-10-21 | |
| 26.x.x (LTS transition) | 2026-10-28 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the release schedule table in the issue and compare the listed v26.x dates and releasers with the current release plan. Done means the schedule is current and the placeholder entries are resolved, but the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100