fix(node): keep odd versions Current through maintenance window#242
Merged
CalvinAllen merged 1 commit intomainfrom Apr 20, 2026
Merged
fix(node): keep odd versions Current through maintenance window#242CalvinAllen merged 1 commit intomainfrom
CalvinAllen merged 1 commit intomainfrom
Conversation
Odd-numbered Node.js release lines (e.g., v25) have a maintenance date several weeks before their end date, but no LTS phase. The lifecycle resolver was mapping that window directly to EOL, so v25.9.0 rendered as EOL despite still being the Current release per nodejs.org. Treat the post-maintenance, pre-end window as Current for odd versions to match nodejs.org's release schedule page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dtvem list-all nodewas marking v25.x as EOL even though Node.js still lists it as Current (v26 hasn't released yet, v25's actual end date is 2026-06-01).src/runtimes/node/lifecycle.go, any odd (non-LTS) release that passed itsmaintenancedate was short-circuited toEOL, skipping the ~2-month maintenance window beforeend.endis still EOL.Resolves DTVEM-241
Test plan
TestLifecycleProvider_VersionStatus/v23_odd_version_in_maintenance_window_is_still_Currentv25_past_maintenance_but_before_end_is_Current(now=2026-04-20, v25.9.0)./rnr checkpasses (format, lint, full test suite)dtvem list-all nodeagainst a real install and confirm v25.x rows now readCurrent