Skip to content

Node.js Release Working Group

JavaScript · active 2025-02-142026-07-07 (UTC)

Partial coverage11,772 / 13,099 hourly files (90%) · 2 absent upstream · 1,323 failed, retryable2025-02-112026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
393
Pushes
17
Pull requests
14
Issues
27
Stars
112
Forks
40

Activity over time

Daily event counts in the loaded window

Line chart, 509 days from 2025-02-14 to 2026-07-07. Pushes: 17 total, peak 3 in a day. Pull requests: 14 total, peak 4 in a day. Issues: 27 total, peak 4 in a day. Comments: 127 total, peak 16 in a day. Stars: 112 total, peak 3 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue#1157openjs-meetings-bot[bot]2026-05-22 01:10
    Node.js Release WorkGroup Meeting 2026-05-28
  • Issue comment#1154aduh952026-04-30 15:09
    What would be the versioning style during Alpha period
  • Issue#1141RafaelGSS2026-04-02 14:31
    Node.js Release WorkGroup Meeting 2026-03-05
  • Issue#1139RafaelGSS2026-04-02 14:31
    Node.js Release WorkGroup Meeting 2026-01-08
  • Issue#1140RafaelGSS2026-04-02 14:31
    Node.js Release WorkGroup Meeting 2026-02-12
  • Issue#1117RafaelGSS2026-04-02 14:31
    Node.js Release WorkGroup Meeting 2025-08-21
  • Issue comment#953trivikr2026-03-31 19:53
    Proposal for new release schedule / users are not interested in releases that will not become LTS
  • Pull request#1109aduh952026-03-13 08:35
  • Issue comment#1142aduh952026-03-11 16:15
    Proposal - change the prerelease phase name to something else
  • Issue comment#1143aduh952026-03-11 13:24
    Proposal - extend the "Current" Release Phase to 12 Months
  • Issue comment#1143trivikr2026-03-11 00:45
    Proposal - extend the "Current" Release Phase to 12 Months
  • Issue comment#1143aduh952026-03-10 23:11
    Proposal - extend the "Current" Release Phase to 12 Months
  • Issue comment#1113trivikr2026-03-05 19:04
    Proposal - Shift Node.js to Annual Major Releases and Shorten LTS Duration
  • Issue comment#1062MikeMcC3992026-02-24 19:57
    doc: add codenames through to Node.js 54 (2040)
  • Issue#1140openjs-meetings-bot[bot]2026-01-30 00:44
    Node.js Release WorkGroup Meeting 2026-02-05
  • Issue comment#1127rubimoutlook740-bot2026-01-23 07:50
    Node.js Release WorkGroup Meeting 2025-11-13
  • Issue comment#1134rubimoutlook740-bot2026-01-23 07:49
    Node.js Release WorkGroup Meeting 2025-12-11
  • Issue comment#1128rubimoutlook740-bot2026-01-23 07:49
    Switch to LFX for meetings
  • Issue comment#1134rubimoutlook740-bot2026-01-23 07:49
    Node.js Release WorkGroup Meeting 2025-12-11
  • Issue comment#1135rubimoutlook740-bot2026-01-23 07:48
    Move regular releases after security release annoucement
  • Issue comment#1135rubimoutlook740-bot2026-01-23 07:48
    Move regular releases after security release annoucement
  • Issue comment#1135rubimoutlook740-bot2026-01-23 07:48
    Move regular releases after security release annoucement
  • Issue comment#953rubimoutlook740-bot2026-01-23 07:48
    Proposal for new release schedule / users are not interested in releases that will not become LTS
  • Issue comment#953rubimoutlook740-bot2026-01-23 07:47
    Proposal for new release schedule / users are not interested in releases that will not become LTS
  • Issue comment#953rubimoutlook740-bot2026-01-23 07:46
    Proposal for new release schedule / users are not interested in releases that will not become LTS

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 112 stars here means stars gained during the window, not the repo's star count.