Use shared ubuntu-latest runner label for publish workflow #3

Merged

troed merged 1 commit from fix/workflow-runner-label into main

2026-08-07 19:30:23 +02:00

troed commented

2026-08-07 19:29:59 +02:00

Owner

Summary

Change the publish workflow's runs-on: docker → runs-on: ubuntu-latest so it matches the runner label already registered on this Forgejo instance (used by the troed/computer project). A runner only picks up jobs whose runs-on matches one of its configured labels, which is why run #3453 for the v0.1.0 tag stayed stuck in "waiting".
Add a workflow test asserting the ubuntu-latest label (and that docker is gone) to prevent regressions.

Test Plan

npx jest — 15 suites / 94 tests passing
Merge, then git tag v0.1.0 && git push origin v0.1.0 (or re-tag) and confirm the workflow completes and the npm package appears at https://git.sync.wtf/troed/-/packages/npm/peertube-plugin-peeryou

## Summary - Change the publish workflow's `runs-on: docker` → `runs-on: ubuntu-latest` so it matches the runner label already registered on this Forgejo instance (used by the troed/computer project). A runner only picks up jobs whose `runs-on` matches one of its configured labels, which is why run #3453 for the `v0.1.0` tag stayed stuck in "waiting". - Add a workflow test asserting the `ubuntu-latest` label (and that `docker` is gone) to prevent regressions. ## Test Plan - [x] `npx jest` — 15 suites / 94 tests passing - [ ] Merge, then `git tag v0.1.0 && git push origin v0.1.0` (or re-tag) and confirm the workflow completes and the npm package appears at https://git.sync.wtf/troed/-/packages/npm/peertube-plugin-peeryou

troed added 1 commit

2026-08-07 19:29:59 +02:00