ci: bound release and dataset jobs with explicit timeouts - #853
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Merged
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.
Purpose
Maintenance plan §8.1 (CI waste removal without reducing verification) — residual gap closure. Investigation found §8.1 substantially already shipped in
test.yml: per-PRconcurrencywithcancel-in-progressscoped topull_requestevents only (group keys workflow + event + ref + PR number), workflow-levelpermissions: contents: read,timeout-minutes: 15on all three jobs, and the Node-matrix duplication finding recorded in-file (lts/*currently resolves to 24.20.0; a fixed 24 entry would duplicate it — matrix intentionally unchanged, floatingtest (lts/*)is a required check).release.ymlalready has its dedicatedpatina-release-publicationgroup withcancel-in-progress: false(release publication can never be cancelled by PR runs) and minimal per-job permissions.The only §8.1 element missing was explicit job timeouts on
release.ymlandpublish-dataset.yml. This PR adds exactly those.Changes (6 lines, workflows only)
Observed release-run durations: 2026-09-10 success ≈3 min; 2026-09-15 failure ≈42 min (auth failure + waiting) — bounds are ≥3x observed successes.
Not changed
No check name, job, matrix entry, trigger, permission, or concurrency group is added, removed, or renamed. No Node-floor or matrix change (out of scope per plan; existing in-file finding stands). The #850 Redis quality steps are untouched.
Verification
test.yml(unchanged) — timeouts on release jobs are exercised on the next release run; failure mode is a bounded kill instead of an unbounded hang, rollback = revert this PR.