Repository navigation
Open
Labels
area:processRepo-wide process, governance, privacy and security rulesRepo-wide process, governance, privacy and security ruleskind:taskBounded delivery task with a delegated sliceBounded delivery task with a delegated slice
Description
Tracks the rollout accepted in #540. Implementation: #541. Release operations and the checked-in v0.3.0 highlights are owned by @zengchuang-hw. Independent rehearsal sign-off is requested from @Dong1017, who reviewed the implementation. Record the actual signer and their decision here before enabling publication.
- Record expectations before dispatch. Once Publish weekly stable minor releases alongside daily patch previews #541 is on the default branch, record the dispatch SHA, latest stable tag, latest numeric release and highest numeric reservation. For the v0.2.x series with v0.2.0 as the previous stable and no later minor reserved, expect v0.3.0, stable, with notes starting at v0.2.0. A later v0.2.x preview changes the numeric baseline only. If reservations or the stable baseline have changed, record the recalculated expectations first.
- Rehearse on the default branch. Confirm
INFERRSI_WEEKLY_RELEASE_ENABLEDis unset or false. Useweekly=trueanddry_run=trueon a tree that differs from the latest stable. A commit already published as a preview is eligible. Dry runs bypass the activation guard and obey the normal weekly skip rules. A skipped build leaves this item open. - Attach the Actions run and evidence. Check the planned tag and
prerelease=false, previous stable notes baseline, and the checked-in highlights (docs/release-notes/v0.3.0.mdfor this series). Verify the wheel, sdist, Codex ZIP, WorkSwarm ZIP and SHA256SUMS from the fresh build. Confirm the publish job skipped, the target has no new tag or Release, and the prior Latest designation stayed in place. - Enable after independent sign-off. Record the review of that specific run, then set
INFERRSI_WEEKLY_RELEASE_ENABLED=truebefore Sunday 08:00 Asia/Shanghai. If the window is missed, the next scheduled attempt is the following Sunday. An out-of-schedule live dispatch would require a separate release decision. - Verify live publication. The release owner checks the release-bot run and records its URL, commit, tag, stable and Latest designation, previous stable notes baseline, asset names and checksums. Verify the next eligible daily release is a patch preview (v0.3.1 after v0.3.0, absent reservations) and Latest continues to refer to the stable release. Sunday’s 02:00 preview may precede the weekly release on the same source.
- If rollout fails, disable the weekly variable, record the run and check the actual tag, draft, assets and Latest pointer. A failure before publication leaves the previous stable as Latest. Preserve reservations and evidence. Handle any published correction under a new version.
Scope covers a dry run followed by separate enablement and verification of the first scheduled stable release.
Metadata
Metadata
Assignees
Labels
area:processRepo-wide process, governance, privacy and security rulesRepo-wide process, governance, privacy and security ruleskind:taskBounded delivery task with a delegated sliceBounded delivery task with a delegated slice
Activity
Dong1017 commentedon Nov 21, 2026
Posted by Dong-bot, an automated agent acting on behalf of @Dong1017 (always-on-bot, model claude-sonnet-5-5).
Assessment: This is a sound, narrowly scoped activation checklist for the rollout accepted in #540. It keeps the rehearsal and enablement separate from the implementation PR #541. The four steps follow the #540 decision: land the code with the weekly path guarded, do one
workflow_dispatchdry run, enable the weekly cron separately, then verify the first live run. I read #540 and #541 (PR description and thread). I did not read the workflow or planner code, and I ran nothing.Gaps to close before step 1 is treated as done
v0.2.0, latest numericv0.2.7, both subject to change by dispatch time), the check would be:v0.3.0, with patch 0 and a new tag with a fresh build rather than a reuse of the preview.docs/release-notes/v0.3.0.mdis picked up by the generalizedvX.Y.Z.mdlookup, so the notes contain the checked-in highlights rather than only generated text.INFERRSI_WEEKLY_RELEASE_ENABLEDgates only the scheduled weekly cron and notworkflow_dispatch. If it also gated dispatch, step 2 could not be done before step 3. Please also confirm that the variable is unset or false during the rehearsal. Otherwise the rehearsal doesn't prove the guard works.0 0 * * 0UTC, which is Sunday 08:00 CST. Set the variable well before that, and say how the first run will be watched. The Sunday 02:00 CST daily run publishes a preview first. That is expected, and the weekly run should still planv0.3.0. If the variable is set after a missed window, the first stable slips by a week. Decide whether a manual non-dry-run dispatch is an acceptable fallback.v0.3.1with Latest unchangedSuggested next step: Edit the body to add the expected-values list from item 1, and mention the target dispatch SHA once #541 has merged. Item 2 (dispatch independent of the variable) is the one I'd settle before dispatching.
Step 1 is blocked until #541 reaches the default branch. Nothing here is actionable on a live release before then.
Dong-bot (authorized delegate).
amy-why-3459 commentedon Nov 21, 2026
This updated checklist is a clear activation record, kept separate from the implementation in #541. It already closes the main gaps from the earlier triage: expectations are pinned (and must be recalculated if the stable or numeric baseline or reservations move), the dry run must exercise a build, sign-off is independent, enablement timing is explicit, live-run evidence is listed, and a failure/rollback path is included. An out-of-schedule live dispatch correctly requires a separate release decision rather than being an implicit fallback.
The current #541 head
880bc080c2d0322863e14ca7a8eb53e78efbe8eanow gates live weekly publication onINFERRSI_WEEKLY_RELEASE_ENABLED, leaves weeklyworkflow_dispatchdry runs available while that variable is unset or false, and points here for the rehearsal record. That matches items 2–4. I reviewed that increment on the PR; this comment is not a substitute for the default-branch dry run.Step 2 remains blocked until #541 reaches the default branch. When it does, please write the actual dispatch SHA, latest stable tag, latest numeric release and highest reservation into this issue before dispatching, then compare the Actions run against those recorded values.