# Node.js Release WorkGroup Meeting 2026-03-05

## Links

* **Recording**:
* **GitHub Issue**: https://github.com/nodejs/Release/issues/1141
* **Minutes**: https://hackmd.io/@openjs-nodejs/r1VSFv0_Ze

## Present

* Antoine
* Juan
* Marco
* Rafael
* Richard
* Ruy

## Agenda

## Announcements

*Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.

Releases of:

* v25.8.0
* v22.22.1
* v20.20.1

### nodejs/nodejs.org

* Blog: Evolving the Node.js Release Schedule [#8631](https://github.com/nodejs/nodejs.org/pull/8631)
* Ping Ulises to know what are the reasons to not land that as soon as possible.

### nodejs/Release

* Release plan - v25.x Current [#1122](https://github.com/nodejs/Release/issues/1122)
* Included Rafael name on the queue for the next v25 release.

* Release plan - v24.x Current [#1089](https://github.com/nodejs/Release/issues/1089)

* Release plan - v22.x Maintenance LTS [#1001](https://github.com/nodejs/Release/issues/1001)
* There's a npm security release that we might make us to issue a new release of v22.x. This won't be necessary for v20 as it will be EOL.

* Release plan - v20.x Maintenance LTS [#855](https://github.com/nodejs/Release/issues/855)
* Discussion on backporting npm 10 to v20. Richard provide some
information on what prevent us to backport npm 10 to v20 line.

* Proposal - Shift Node.js to Annual Major Releases and Shorten LTS Duration [#1113](https://github.com/nodejs/Release/issues/1113)
* Proposal for new release schedule / users are not interested in releases that will not become LTS [#953](https://github.com/nodejs/Release/issues/953)

### nodejs/node

* tools: add a backport queue cron action [#56143](https://github.com/nodejs/node/pull/56143)
* No updates this week

## Q&A, Other

## Upcoming Meetings

* **Node.js Project Calendar**: <https://nodejs.org/calendar>

Click `Add to Google Calendar` at the bottom left to add to your own Google calendar.