|
Ran
|
Jobs
2
|
Files
339
|
Run time
1min
|
Badge
README BADGES
|
push
github
fix(ci): make the release workflow agree with the actions lockfile (#1158) ## Root cause `nostream@3.16.0` published with no container image. Run [43985051541](https://github.com/cameri/nostream/actions/runs/43985051541) ended in `startup_failure` — no job was ever created — because the workflow file itself will not parse: ``` failed to parse workflow: Invalid dependency lockfile ".github/workflows/actions.lock": workflow ".github/workflows/release.yml" references actions not present in the lockfile: docker/login-action@<a class=hub.com/cameri/nostream/commit/f054a8b539a109f9f41c372932f1ae047eff08c9">f054a8b53<a href="https://github.com/cameri/nostream/commit/026bd008160aac57dae358721ddaeca58c72daad">, docker/metadata-action@<a class=hub.com/cameri/nostream/commit/98669ae865ea3cffbcbaa878cf57c20bbf1c6c38">98669ae86<a href="https://github.com/cameri/nostream/commit/026bd008160aac57dae358721ddaeca58c72daad">, docker/build-push-action@<a class=hub.com/cameri/nostream/commit/ad44023a93711e3deb337508980b4b5e9bcdc5dc">ad44023a9 ``` `release.yml` pinned those three actions by full commit SHA; `actions.lock` (added in #1117) records them by tag. The lockfile check compares the two strings, so the mismatch makes the file unparseable. The three actions were the only mismatch — the other six workflows already reference the tags their entries record, and the last good release (`nostream@3.15.3`, run [43552967942](https://github.com/cameri/nostream/actions/runs/43552967942)) predates #1117. ## What changed Three `uses:` lines in `.github/workflows/release.yml`, regenerated with `gh actions-lock` v0.4.1: | | before | after | |---|---|---| | login | `docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9` | `docker/login-action@v1.10.0` | | metadata | `docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38` | `docker/metadata-action@v3.3.0` | | build-push | `docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc` | `docker/build-push-action@v2.5.0` | The lockfile is **unchanged**: its entries for those three actions already recorded exactly those commits (`sha1-f054a8b…`, `sha1-98669ae…`, `sha1-ad44023…`). Nothing about which commit runs has moved; the workflow now names the tag, and the lockfile pins the commit, which is the shape this repo adopted in #1117 ... (continued)
5438 of 7451 branches covered (72.98%)
Branch coverage included in aggregate %.
11473 of 13890 relevant lines covered (82.6%)
678.09 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | Unit - 43991451057.1 | 339 |
77.12
|
GitHub Action Run | |
| 2 | Integration - 43991451057.2 | 339 |
34.94
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|