bvandeusenandClaude Opus 5 059e2128ee fix(ci): stop telling readers the runner can't run upload-artifact@v4+ ...

build.yml and baseline.yml both explained a missing artifact step by
saying act_runner cannot run actions/upload-artifact@v4+ (and baseline.yml
said ci-requirements.md records that, which it does not). The runner is
now gitea/runner 3.x, which edits the action's GHES refusal out of its
bundle, and stock v4+ is proven working on this forge (Scribe spike #3843).

Comments only. Neither lane gains an upload step: build-web still reads
the signed XPI from the release asset, and the baseline candidate is
still printed to the log, because those remain the better channels. The
comments now say why for the right reason.

Scribe snippet #2271, milestone 395.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DwoKYuw3qJmUUYsJeNherB

2026-09-10 17:43:36 -04:00

..

baseline.yml

fix(ci): stop telling readers the runner can't run upload-artifact@v4+

2026-09-10 17:43:36 -04:00

build.yml

fix(ci): stop telling readers the runner can't run upload-artifact@v4+

2026-09-10 17:43:36 -04:00

ci.yml

docs+ci: folder import stays retired, and fix a readiness probe that never probed

2026-09-02 00:51:25 -04:00

extension.yml

ci(extension): retire the manual-bump guard, true up the docs (step 5)

2026-08-27 11:29:44 -04:00

release.yml

ci: a release publishes a changelog, not an image (318 step 7)

2026-08-28 20:57:25 -04:00