Commit ab57b23
committed
fix(release): gate on the last released tag, not the working tree
The gate asked whether anything moved since the last commit, so a
regeneration committed by hand left a clean tree and the next scheduled
run reported success while skipping every publish step. Nothing alerts,
because skipping is what the gate exists to do.
Compare the spec at the last release tag against the freshly regenerated
copy instead, which answers whether what is published was built from the
current spec. This needs fetch-depth 0, since the default checkout
fetches no tags and a missing tag reads as never released.1 parent e15fb07 commit ab57b23
1 file changed
Lines changed: 23 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
23 | 23 | | |
24 | 24 | | |
25 | 25 | | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
26 | 30 | | |
27 | 31 | | |
28 | 32 | | |
| |||
35 | 39 | | |
36 | 40 | | |
37 | 41 | | |
38 | | - | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
39 | 51 | | |
40 | 52 | | |
41 | | - | |
42 | | - | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
43 | 62 | | |
44 | | - | |
| 63 | + | |
45 | 64 | | |
46 | 65 | | |
47 | 66 | | |
| |||
0 commit comments