Commit ad42f29
feat(ci): auto-tag and release on version bump to master (v2.4.3)
Previously a release required pushing a `v*` tag manually, and a
separate gate-release job verified the tag was reachable from master.
Drop that whole flow in favour of a simpler model:
1. PR is opened: matrix runs for verification only.
2. PR merges to master: matrix runs again. If every job succeeds AND
the package.json version on the merge commit has no matching
`v<version>` tag on origin yet, the release job:
- creates the tag pointing at the merge commit
- creates a GitHub Release named after the tag
- uploads the prebuild tarballs as release assets
The tag is created by softprops/action-gh-release using the
built-in GITHUB_TOKEN, so it does not cascade back into the
workflow.
3. Master push without a version bump: matrix runs, release step
sees the tag already exists, skips. No-op release.
Cutting the first release of this flow by bumping to 2.4.3.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent fc240c4 commit ad42f29
3 files changed
Lines changed: 42 additions & 36 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
7 | 6 | | |
8 | 7 | | |
9 | 8 | | |
| |||
135 | 134 | | |
136 | 135 | | |
137 | 136 | | |
138 | | - | |
139 | | - | |
140 | | - | |
141 | | - | |
142 | | - | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
143 | 144 | | |
144 | | - | |
| 145 | + | |
145 | 146 | | |
146 | | - | |
147 | | - | |
| 147 | + | |
| 148 | + | |
148 | 149 | | |
149 | 150 | | |
150 | | - | |
151 | | - | |
152 | | - | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
153 | 163 | | |
154 | 164 | | |
155 | | - | |
156 | | - | |
157 | | - | |
158 | | - | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
159 | 169 | | |
160 | | - | |
161 | | - | |
162 | | - | |
| 170 | + | |
| 171 | + | |
163 | 172 | | |
164 | 173 | | |
165 | | - | |
166 | | - | |
167 | | - | |
168 | | - | |
169 | | - | |
170 | | - | |
171 | | - | |
172 | | - | |
173 | | - | |
174 | | - | |
175 | 174 | | |
| 175 | + | |
176 | 176 | | |
177 | 177 | | |
178 | 178 | | |
179 | 179 | | |
180 | 180 | | |
181 | 181 | | |
182 | 182 | | |
| 183 | + | |
183 | 184 | | |
184 | 185 | | |
185 | | - | |
| 186 | + | |
| 187 | + | |
186 | 188 | | |
187 | 189 | | |
188 | | - | |
189 | | - | |
190 | | - | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
191 | 197 | | |
192 | 198 | | |
193 | 199 | | |
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
0 commit comments