nodejs/Release
Release
The Node.js Release repository is the official tooling and process definition for managing the release lifecycle of the Node.js runtime itself. It implements a time-based branching model that creates new major version branches from the main line every six months, with even-numbered lines designated for Long-Term Support (LTS) and odd-numbered lines remaining as Current releases. The project defines a strict state machine that governs how each release line transitions through Current, Active LTS, and Maintenance phases, each with its own rules for what changes may land.
The repository provides a staging-branch cherry-pick pipeline that isolates backported changes for each LTS line, ensuring that commits land on a staging branch before being cut into a release. It also generates and publishes machine-readable JSON schedules that detail each Node.js version's release date, support phases, and end-of-life deadlines, enabling external automation tools and deployment pipelines to consume this lifecycle data programmatically. The release schedule management capabilities forecast when versions will enter Active LTS, shift to Maintenance, and reach end-of-life, allowing teams to plan upgrades in advance.
The project covers the full scope of Node.js version lifecycle tracking, from classifying release phases to managing branch creation and coordinating update eligibility across multiple version lines. Its documentation and tooling are designed to be consumed by both human operators and automated systems, with the machine-readable schedule exports serving as the primary integration surface for external automation.
Features
- Release Data Exporters - Exports Node.js version schedules as machine-readable JSON files for external automation integration.
- Version Transition Forecasts - Forecasts planned dates for Node.js version transitions through Active LTS, Maintenance, and end-of-life.
- Release Schedule Exports - Exports machine-readable JSON schedules detailing Node.js version release dates and support phases.
- Release Phase Definitions - Classifies Node.js release lines into Current, Active LTS, or Maintenance phases with change eligibility rules.
- Release Phase Queries - Classifies every Node.js release line by phase so users know which versions receive updates.
- Staging Branch Pipelines - Maintains separate staging branches per LTS line for cherry-picked commits before release cuts.
- Staging Branch Cherry-Pick Pipelines - Maintains staging branches per release line where cherry-picked commits land before release cuts.
- Fixed Cadence Release Triggers - Triggers new major version branches on a fixed six-month schedule independent of feature readiness.
- LTS Line Staging Branches - Provides dedicated staging branches for each LTS line to isolate backported changes before release.
- Long-term Support Policies - Manages Node.js version transitions through Current, Active LTS, and Maintenance phases for update eligibility.
- Release Phase Classifiers - Categorizes Node.js versions into Current, Active LTS, or Maintenance phases with update eligibility rules.
- Version Lifecycle Trackers - Monitors Node.js version support phases and end-of-life dates to coordinate system upgrades.
- Release Lifecycle Trackers - Tracks Node.js version dates, support phases, and end-of-life deadlines for upgrade coordination.
- Release Schedule Managers - Publishes machine-readable JSON schedules defining each Node.js version's release date, support phases, and end-of-life deadline.
- Major Release Schedulers - Branches new semver-major Node.js versions from main every six months with LTS or Current designation.
- Release Timeline Tracking - Generates machine-readable JSON files mapping each Node.js version to its current support phase, start date, and end-of-life date.
- Release Phase State Machines - Implements a state machine governing Node.js version transitions through Current, Active LTS, and Maintenance phases.
- Semver-Major Branching Models - Creates semver-major branches from main every six months, alternating between LTS and Current lines.
- Release Lifecycle Management - Tracks Node.js release dates, support phases, and end-of-life deadlines across multiple version lines.
- LTS Branch Managers - Maintains separate staging and release branches for Node.js LTS lines to manage backported changes.
