Skip to content

Let stable 0.6.0 promote the newest rc without a soak - #69

Merged
shipmill-romamo[bot] merged 1 commit into
mainfrom
release/soak-zero
Oct 10, 2026
Merged

shipmill-romamo[bot] merged 1 commit into
mainfrom
release/soak-zero

Conversation

@shipmill-romamo

Copy link
Copy Markdown
Contributor

Decision by @romamo, given in chat: release 0.6.0 now from the newest rc instead of waiting for rc7's 3-day soak (2026-10-12).

  • [lanes.stable] min_soak_days 3 → 0, for this release only
  • After merge: the Release workflow is started by hand with lane: stable (dry run first), promoting the newest rc (rc13 at the time of writing)
  • Right after 0.6.0 is out, a follow-up PR sets min_soak_days back to 3

No CHANGELOG entry: a policy change, not a change to the package.

🤖 Generated with Claude Code

Roman decided to release 0.6.0 now instead of on 2026-10-12, so the
stable lane can be started by hand from the newest rc. The soak goes
back to 3 days right after the release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@shipmill-romamo
shipmill-romamo Bot merged commit 523b6c9 into main Oct 10, 2026
1 check passed
@shipmill-romamo
shipmill-romamo Bot deleted the release/soak-zero branch October 10, 2026 04:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant