ci(node): add weekly workflow to refresh release schedule#243
Merged
CalvinAllen merged 1 commit intomainfrom Apr 20, 2026
Merged
ci(node): add weekly workflow to refresh release schedule#243CalvinAllen merged 1 commit intomainfrom
CalvinAllen merged 1 commit intomainfrom
Conversation
The embedded schedule.json was committed once and had no refresh mechanism, so upstream changes from nodejs/Release would silently drift. Add a scheduled workflow that pulls the upstream file each Monday and commits only when it differs, matching the direct-commit pattern used by the manifest regeneration workflow.
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
src/runtimes/node/data/schedule.json(the embedded Node.js release schedule used by the lifecycle resolver) was committed once in feat(lifecycle): add Node.js lifecycle status to list-all command #238 and had no refresh mechanism.nodejs/Releasegets revised (new majors, shifted EOL dates, revised maintenance windows), so the embedded copy will silently drift.schedule.jsonevery Monday at 06:00 UTC and commits it only if it differs, using the same direct-commit-to-main pattern asgenerate-manifests-from-r2.yml.Test plan
Actions → Refresh Node.js Schedule → Run workflow) and confirm the job summary reads "No changes" (file was verified in sync during the [Bug]: Node status is listing current version as EOL #241 investigation)CONTRIBUTORS_TOKENhas push permission (reused from the manifests workflow, so should be fine)schedule.jsonon a throwaway branch and dispatch to confirm the commit step fires