Commit e18503d
committed
GH Actions/verify release: tweak the workflow [2]
PHIVE does not support a "stability" flag yet, which means that it will always grab the very latest release, even when this is an alpha/beta/RC pre-release.
As the GH API `releases/latest` route returns the latest _stable_ release, this causes the workflow to fail.
This was already previously identified as an area which needed attention in #758, and as we now have a pre-release as the latest release (`4.0.0beta1`), this now needs to be fixed.
Note: this still doesn't fix things completely, as in reality, the workflow should work based on the tag published if the workflow is triggered by a release to ensure that the "release assets" and "versioned web" jobs check the right release ("unversioned web" should still always check the latest stable release), but it is unclear where to grab that info from and as testing the info available when the workflow is triggered by a release requires doing a release, this is neigh impossible to test. I may need to create a dummy repo just to test.
For now, this at least fixes the Phive jobs.1 parent 45b7a3a commit e18503d
1 file changed
+16
-12
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
148 | 148 | | |
149 | 149 | | |
150 | 150 | | |
151 | | - | |
152 | | - | |
153 | | - | |
154 | | - | |
155 | | - | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
156 | 160 | | |
157 | 161 | | |
158 | 162 | | |
159 | | - | |
160 | | - | |
161 | | - | |
| 163 | + | |
| 164 | + | |
162 | 165 | | |
163 | | - | |
| 166 | + | |
| 167 | + | |
164 | 168 | | |
165 | | - | |
166 | | - | |
| 169 | + | |
| 170 | + | |
167 | 171 | | |
168 | | - | |
| 172 | + | |
169 | 173 | | |
170 | 174 | | |
171 | 175 | | |
| |||
0 commit comments