Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Node.js Release WorkGroup Meeting 2026-09-17

Open
#1,180 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
node.js
Domain
release

Research direction

This issue records a scheduled Node.js Release WorkGroup meeting rather than a code change. Start with the meeting time, agenda, and linked HackMD minutes; there are no repository files or tests named. The record is complete when the meeting details, agenda, and minutes link are accurate.

Written by the indexing model from the issue text.

Description

Time

UTC Thu, Sep 17, 2026, 02:00 PM:

Timezone Date/Time
US / Pacific Thu, Sep 17, 2026, 07:00 AM
US / Mountain Thu, Sep 17, 2026, 08:00 AM
US / Central Thu, Sep 17, 2026, 09:00 AM
US / Eastern Thu, Sep 17, 2026, 10:00 AM
EU / Western Thu, Sep 17, 2026, 03:00 PM
EU / Central Thu, Sep 17, 2026, 04:00 PM
EU / Eastern Thu, Sep 17, 2026, 05:00 PM
Moscow Thu, Sep 17, 2026, 05:00 PM
Chennai Thu, Sep 17, 2026, 07:30 PM
Hangzhou Thu, Sep 17, 2026, 10:00 PM
Tokyo Thu, Sep 17, 2026, 11:00 PM
Sydney Fri, Sep 18, 2026, 12:00 AM

Or in your local time:

Links

Invited

  • Release team: @nodejs/release
  • LTS team: @nodejs/lts
Observers/Guests

None.

Agenda

Issues and Pull Requests

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

nodejs/citgm
  • doc: add BethGriggs to CITGM team #1139
nodejs/Release
  • Alpha phase for Node.js 27 unexplained #1160
  • Release plan – v26.x Current #1152
  • Release plan - v24.x Active LTS #1089
  • Release plan - v22.x Maintenance LTS #1001

Joining the meeting


Invitees

Please use the following emoji reactions in this post to indicate your availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure
Dominant language
JavaScript
Stars
4.4k
Forks
675
Avg merge
22h 29m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/Release

All issues in nodejs/Release

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.