fix(ci): run the tag job on this repo's own pool, host-mode #2

Merged

rcsheets merged 1 commit from feat/attribution-and-backfill into main

2026-08-09 21:44:27 +00:00

rcsheets commented

2026-08-09 06:22:41 +00:00

Owner

The tag job was written for [dind, trusted] on the assumption that those
labels named a shared pool, because gllm and pr-reviewer both use them. They do
not. Every pool on this forge is scope: repository, so those labels resolve to
each of those repos' own pools and to nothing at all here -- and borrowing
another repo's pool is not an arrangement this forge permits. As merged in #1,
the job would have queued forever.

changelog-action now has a pool of its own (brooktrails/infra
apps/forgejo/runner/runnerpool-changelog-action.yaml, merged separately),
labelled changelog-action. It has no DinD sidecar, so jobs run host-mode --
directly in the runner pod -- which means this workflow must not set a
container:. The install step goes with it: the pool's image already carries
git.

Corrects the runner claim in #1, whose commit message asserted a shared pool
that does not exist.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

The tag job was written for `[dind, trusted]` on the assumption that those labels named a shared pool, because gllm and pr-reviewer both use them. They do not. Every pool on this forge is `scope: repository`, so those labels resolve to each of *those* repos' own pools and to nothing at all here -- and borrowing another repo's pool is not an arrangement this forge permits. As merged in #1, the job would have queued forever. changelog-action now has a pool of its own (brooktrails/infra `apps/forgejo/runner/runnerpool-changelog-action.yaml`, merged separately), labelled `changelog-action`. It has no DinD sidecar, so jobs run host-mode -- directly in the runner pod -- which means this workflow must not set a `container:`. The install step goes with it: the pool's image already carries git. Corrects the runner claim in #1, whose commit message asserted a shared pool that does not exist. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

rcsheets added 1 commit

2026-08-09 06:22:41 +00:00

ci: tag releases from conventional commits, and move the major alias 44eb229d0d

This repo had no workflows, so its tags were placed by hand -- the one
thing the projects consuming it never do. The version now comes from the
conventional commits since the last vX.Y.Z, same rule they use.

The part specific to being an action repo is the alias. Callers
reference changelog-action@v1, which is a tag rather than a branch, so
merging to main changes nothing for them until v1 moves. Tagging only
vX.Y.Z would leave every consumer on the old code with no sign that
anything had shipped, so the job pushes the exact version and then
force-moves the alias onto it. A failure there fails the job: a new
vX.Y.Z beside a stale vN is a release nobody receives, which should be
loud rather than a green run that changed nothing.

Runs on the shared [dind, trusted] pool, this forge's arrangement for a
repo without its own runner pool.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

rcsheets force-pushed feat/attribution-and-backfill from 44eb229d0d to 65c6876709

2026-08-09 13:03:42 +00:00

Compare

rcsheets changed title from ~~ci: tag releases from conventional commits, and move the major alias~~ to fix(ci): run the tag job on this repo's own pool, host-mode

2026-08-09 13:06:59 +00:00

rcsheets merged commit f2416ad30a into main

2026-08-09 21:44:27 +00:00

rcsheets deleted branch feat/attribution-and-backfill

2026-08-09 21:44:27 +00:00

rcsheets referenced this pull request from a commit

2026-08-09 21:44:27 +00:00

Merge pull request 'fix(ci): run the tag job on this repo's own pool, host-mode' (#2) from feat/attribution-and-backfill into main