Two fixes found while rewriting runneros on this layout. The runneros pipeline tested both.
Checkout: gitea-runner 6.0.0 removed builtin:checkout (runner#1407), so 6.x rejects it as an invalid action. The workflow now fetches the commit with git and the job token, without Node.js or an action from GitHub. Setting permissions: keeps contents: read for that and asks for packages: write.
Local test key:mkosi genkey refuses to run while mkosi.crt exists, so the documented local build failed. The docs now make a test key and point a gitignored mkosi.local.conf at it. That covers the Secure Boot, PCR and verity keys, which all need one.
Not fixed here: on this instance, publishing with gitea.token still returns 401 even with packages: write. That looks like the max token permissions in Settings → Actions, so Publish fails until that setting is changed, or until the workflow uses a token secret.
Two fixes found while rewriting runneros on this layout. The runneros pipeline tested both.
- **Checkout:** gitea-runner 6.0.0 removed `builtin:checkout` ([runner#1407](https://gitea.com/gitea/runner/pulls/1407)), so 6.x rejects it as an invalid action. The workflow now fetches the commit with git and the job token, without Node.js or an action from GitHub. Setting `permissions:` keeps `contents: read` for that and asks for `packages: write`.
- **Local test key:** `mkosi genkey` refuses to run while `mkosi.crt` exists, so the documented local build failed. The docs now make a test key and point a gitignored `mkosi.local.conf` at it. That covers the Secure Boot, PCR and verity keys, which all need one.
Not fixed here: on this instance, publishing with `gitea.token` still returns 401 even with `packages: write`. That looks like the max token permissions in Settings → Actions, so Publish fails until that setting is changed, or until the workflow uses a token secret.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
gitea-runner 6 has no builtin:checkout, and plain Fedora has no Node.js
for actions/checkout, so the workflow fetches the commit with git.
Setting permissions: keeps read access for that and asks for package
writes.
mkosi genkey won't replace mkosi.crt, so the docs now sign local builds
with a test key in mkosi.local.conf, which also covers the PCR and
verity keys.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gitea-runner 6 removed builtin:checkout. With Node.js in the job,
actions/checkout works.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Job79
changed title from fix: check out with git, sign local builds with a test key to fix: check out with actions/checkout, sign local builds with a test key2026-11-22 17:05:16 +00:00
actions/checkout needs Node.js in every job and fetches the action from
GitHub. Four lines of git need neither.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Job79
changed title from fix: check out with actions/checkout, sign local builds with a test key to fix: check out with git, sign local builds with a test key2026-11-22 17:41:00 +00:00
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two fixes found while rewriting runneros on this layout. The runneros pipeline tested both.
builtin:checkout(runner#1407), so 6.x rejects it as an invalid action. The workflow now fetches the commit with git and the job token, without Node.js or an action from GitHub. Settingpermissions:keepscontents: readfor that and asks forpackages: write.mkosi genkeyrefuses to run whilemkosi.crtexists, so the documented local build failed. The docs now make a test key and point a gitignoredmkosi.local.confat it. That covers the Secure Boot, PCR and verity keys, which all need one.Not fixed here: on this instance, publishing with
gitea.tokenstill returns 401 even withpackages: write. That looks like the max token permissions in Settings → Actions, so Publish fails until that setting is changed, or until the workflow uses a token secret.🤖 Generated with Claude Code
fix: check out with git, sign local builds with a test keyto fix: check out with actions/checkout, sign local builds with a test keyfix: check out with actions/checkout, sign local builds with a test keyto fix: check out with git, sign local builds with a test keyView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.