Repository navigation
Commit b3dd0ee
ci: release on demand and gate publishing on approval
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>1 parent d684100 commit b3dd0ee
2 files changed
Lines changed: 8 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
15 | 15 | | |
16 | 16 | | |
17 | 17 | | |
| 18 | + | |
18 | 19 | | |
19 | 20 | | |
20 | 21 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| 6 | + | |
6 | 7 | | |
7 | 8 | | |
8 | 9 | | |
9 | 10 | | |
10 | 11 | | |
11 | 12 | | |
12 | 13 | | |
13 | | - | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
14 | 20 | | |
15 | 21 | | |
16 | 22 | | |
| |||
0 commit comments