Skip to content

Verify the first weekly dry run and enable Sunday stable releases #554

Open

Description

@zengchuang-hw

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_ENABLED is unset or false. Use weekly=true and dry_run=true on 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.md for 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=true before 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.

Activity

  1. Dong1017 commented on Nov 21, 2026

    @Dong1017
    Collaborator

    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_dispatch dry 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

    1. Concrete pass criteria for the dry run. Step 2 says "stable minor" and "previous stable" without values. Please record the expected values in the issue before dispatching, then compare them to the run. Using the baseline in Publish weekly Sunday minor releases alongside daily patch previews #540 (latest stable v0.2.0, latest numeric v0.2.7, both subject to change by dispatch time), the check would be:
      • Planned tag is v0.3.0, with patch 0 and a new tag with a fresh build rather than a reuse of the preview.
      • Notes range starts at the last stable tag, not the latest numeric tag. Any preview published since will have moved the numeric baseline, but the notes start must not follow it.
      • docs/release-notes/v0.3.0.md is picked up by the generalized vX.Y.Z.md lookup, so the notes contain the checked-in highlights rather than only generated text.
      • Expected assets and checksums are built, and the publisher step shows as skipped.
      • The plan marks the release as stable with Latest designation, even though dry run suppresses publication.
    2. Dry run must not depend on the enablement variable. Please confirm that INFERRSI_WEEKLY_RELEASE_ENABLED gates only the scheduled weekly cron and not workflow_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.
    3. Dry run must exercise the build. The note that a no-change skip doesn't exercise the build is correct. The rehearsal commit must differ from the latest stable's tree. A same-commit-as-preview run is a good case, since it also checks promotion. Record the dispatch SHA, the stable baseline and the run URL in this issue.
    4. Sign-off independence. The release owner and the sign-off are both @zengchuang-hw, and the sign-off includes the v0.3.0 highlights. Publish weekly stable minor releases alongside daily patch previews #541 also says independent approvals precede integration. For step 3, please name who the "maintainer" is (not the implementer) and have them comment on the rehearsal run.
    5. Timing of enablement and the first-run window. The cron is 0 0 * * 0 UTC, 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 plan v0.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.
    6. Rollback and failure handling. Add a line for what happens if the first live run fails or publishes a wrong release: unset the variable, and don't overwrite or retag an already-published release. Note that Latest stays on the previous stable if the run fails.
    7. Step 4 acceptance list. Spell out the evidence to attach:
      • the tag, and whether it is not a prerelease
      • Latest designation
      • notes range start, which should be the last stable tag
      • asset names and checksums
      • the next daily preview, which should be v0.3.1 with Latest unchanged

    Suggested 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).

  2. amy-why-3459 commented on Nov 21, 2026

    @amy-why-3459
    Collaborator

    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 880bc080c2d0322863e14ca7a8eb53e78efbe8ea now gates live weekly publication on INFERRSI_WEEKLY_RELEASE_ENABLED, leaves weekly workflow_dispatch dry 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.

  3. added
    kind:taskBounded delivery task with a delegated slice
    area:processRepo-wide process, governance, privacy and security rules
    on Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:processRepo-wide process, governance, privacy and security ruleskind:taskBounded delivery task with a delegated slice

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions