nodejs / nodejs/build

Node.js Build WorkGroup Meeting 2026-09-24

Open
#4,474 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jinja
Stars
542
Forks
185
Avg merge
22h 15m
Merged PRs (30d)
4

Description

Time

UTC Thu, Sep 24, 2026, 03:00 PM:

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

Or in your local time:

Links

Invited

  • Build team: @nodejs/build
Observers/Guests

None.

Agenda

Issues and Pull Requests

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

nodejs/build
  • git version(s) for V8 CI #4476
  • Throttle node-test-commit jobs on test CI #4435
  • Build Linux binaries for Node.js 27 on RHEL 9 #4431
  • "CBN" revalidation on the firewall holes for the release team. #4424
  • Node.js 20 End-of-Life action items #4306
  • Out of space on www server #3157

Joining the meeting


Invitees

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

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure

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.

Research direction

No source file, test, or implementation entry point is identified. This issue is an event announcement and agenda for the Node.js Build WorkGroup meeting on September 24, 2026; it is complete as meeting coordination rather than a code change.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.