ci(dev-close-notice): read schedule from tracking issue + post clear-to-merge follow-up#13792
Open
ilhan007 wants to merge 2 commits into
Open
ci(dev-close-notice): read schedule from tracking issue + post clear-to-merge follow-up#13792ilhan007 wants to merge 2 commits into
ilhan007 wants to merge 2 commits into
Conversation
Two updates to the dev-close notice workflow: 1. Extend DEV_CLOSE_PERIODS with the remaining 2026 releases (v2.25–v2.29) sourced from #10568. 2. Add a follow-up 'clear-to-merge' comment. When the workflow runs on a schedule / workflow_dispatch outside a dev-close window, it sweeps every open PR that already carries the dev-close-notice marker and posts a one-shot follow-up telling the author the release has shipped and the PR can now be merged. Idempotent via <!-- dev-close-cleared -->. pull_request events outside a window remain no-ops so we don't churn comments on every event.
Replaces the hardcoded DEV_CLOSE_PERIODS array with a fetch+parse of the release-schedule Markdown table on issue #10568. When the schedule slips a day or two — which happens — the issue is edited in place and the workflow follows on the next run, no PR needed. Parser is column-scoped (Dev Close + Release only) so a typo in the Dev Start column (like the current '103.09.26' for v2.27) doesn't poison the row. Rows with unparseable dates are skipped with a warning rather than failing the whole run. Adds 'issues: read' to the permissions block.
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.
Two updates to the dev-close notice workflow.
1. Read the release schedule from the tracking issue
Instead of hardcoding
DEV_CLOSE_PERIODSin the workflow, the mode-decision step now fetches issue #10568 and parses the release-schedule Markdown table on it. When the schedule slips a day or two — which happens — the issue is edited in place and the workflow follows on the next run, no PR needed.## 2026,## 2027, …) merge into one list — appending next year's schedule is a pure issue edit.permissions.issues: readadded so the workflow canGET /issues/:n.2. Add a follow-up 'clear-to-merge' comment
When the workflow runs on a schedule / workflow_dispatch outside a dev-close window, it now sweeps every open PR that already carries the dev-close-notice marker and posts a one-shot follow-up telling the author the release has shipped and the PR can now be merged.
<!-- dev-close-cleared -->.pull_requestevents outside a window remain no-ops so we don't churn comments on every PR event.RELEASE/RELEASE_DATEare no longer required in clear mode.Test evidence
Parser was run against the current issue #10568 body — all six 2026 rows extracted cleanly. A mocked multi-year body (
## 2026+## 2027) confirms next year's table will be picked up when it's added.Follow-up to #13633.