Repository navigation
docs(freeze-record): fill the 2026-10-18 promotion placeholders - #2537
Merged
Merged
Conversation
The re-docketed-detector entry's staging merge commit, promotion merge commit and merge date, and the live-cadence entry's boundary: promotion/2026-10-18 and its first new-cadence live window, run-pull run 39091707696. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019NtSiNeMSRGjEKSx7yTfdu
This was referenced Oct 18, 2026
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
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.
What
This fills four of the seven placeholders the 2026-10-18 promotion (#2527,
dbb042ca4) left indocs/freeze-record.md, with values read from git and the Actions history.ca25e1285git log --first-parent origin/staging --grep "Merge pull request #2506 "dbb042ca4bd6b6d6f4fcb1f02e0d175ac76d0f2cpromotion/2026-10-18peels to it2026-10-18T01:06:13Zmerged_atis 01:06:14Zpromotion/2026-10-18,dbb042ca4…, run-pull run 39091707696, started2026-10-18T02:53:58ZWhy that run is the boundary.
47 *live crons on main. One is the old47 4,10,16,22; the new one is47 0,2,6,8,12,14,18,20.pullwindow. The firstliverun after it, 39091707696 at 02:53, is in the 02:47 slot, which only the new cron holds. Its jobs showlive: success, and its head36483f458is on main after the merge.Left unfilled: the statpack entry's
refresh commitand its OT2026 and OT2025 pools (~10886). No statpack refresh has reached main since the promotion, so they have no value yet. The first refresh after it fills them.Checks
landed_placeholder_problemsagainst currentmainreturns[]. The two-line live-cadence placeholder is filled by joining its break, which fix(promotion-record): accept a hand fill of a placeholder wrapped across a line break #2508's check now accepts.<,>or backtick.scripts/gate.sh docs-testspasses.Freeze-record fills only, with no owned paths. After docs-reviewer checks the values against their sources, I'll merge into staging myself; the fills reach main at the next promotion.
Generated by Claude Code