Repository navigation
Commit 85268aa
ci: tag releases when a release PR merges (#214)
The push guard from the release-on-demand change never matched. After
the 1.26.0 / 2.27.0 release PRs merged, the push run skipped the
release-please job (sdk-python run 43488257883) even though the merge
commit modifies .release-please-manifest.json, so
contains(toJSON(github.event.commits.*.modified), ...) was false and
nothing was tagged until Release Please was dispatched by hand.
A paths filter on the push trigger does the same job off the pushed
diff, so the job-level guard keeps only the repository check.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>1 parent 41fc333 commit 85268aa
1 file changed
Lines changed: 3 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| 6 | + | |
| 7 | + | |
6 | 8 | | |
7 | 9 | | |
8 | 10 | | |
| |||
13 | 15 | | |
14 | 16 | | |
15 | 17 | | |
16 | | - | |
17 | | - | |
18 | | - | |
19 | | - | |
| 18 | + | |
20 | 19 | | |
21 | 20 | | |
22 | 21 | | |
| |||
0 commit comments