Skip to content

ci: release on demand and gate publishing on approval - #205

Open
spicysouvlaki wants to merge 1 commit into
mainfrom
william/cb-593-release-on-demand
Open

spicysouvlaki wants to merge 1 commit into
mainfrom
william/cb-593-release-on-demand

Conversation

@spicysouvlaki

Copy link
Copy Markdown
Collaborator

Releases become deliberate (CB-593). Release PRs open only when someone runs Release Please, and the PyPI publish waits for approval in the release environment. Merging this doesn't cut a release.

🤖 Generated with Claude Code

CB-593. Until now, every push to main ran release-please, which kept a
release PR open at all times, and merging it published to PyPI through
the release event with no further check. The 1-pager wants publishing to
be a deliberate, manual step.

- release-please.yml now runs on workflow_dispatch, or on a push that
  changes .release-please-manifest.json (a release PR merging), which
  still tags it and creates the GitHub Release. Ordinary pushes no longer
  open or refresh a release PR. The changed-files check works for any
  merge method; matching on the "release: " title wouldn't.
- The publish job runs in the "release" environment, which requires
  William's approval (created 11-04). Manual re-publishes go through the
  same gate.
- No release-as input: release-please-action ignores it in manifest mode.
  To force a version, land a commit with a "Release-As: x.y.z" footer.

stlc treats .github/workflows/* as branch-owned scaffolding, so these
edits survive regeneration and need no re-seal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@spicysouvlaki
spicysouvlaki marked this pull request as ready for review November 4, 2026 00:49
@spicysouvlaki
spicysouvlaki requested a review from a team as a code owner November 4, 2026 00:49
@spicysouvlaki
spicysouvlaki requested a review from jtoar November 4, 2026 00:49
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.

2 participants