Enforce Ubuntu runner policy
This commit is contained in:
@@ -24,6 +24,10 @@ README_COMMAND
|
||||
|
||||
If a command does not exist, document the closest safe alternative. Do not invent commands that cannot run.
|
||||
|
||||
Project build, test, audit, package, installer, dependency setup, and release commands must run on Gitea Ubuntu runners only. Supported labels are `ubuntu-latest`, `ubuntu-24.04`, and `ubuntu-22.04` on `global-runner-1`, `global-runner-2`, and `global-runner-3`.
|
||||
|
||||
Local checks are limited to lightweight validation that does not install dependencies or create build artifacts.
|
||||
|
||||
## Stack
|
||||
|
||||
```text
|
||||
@@ -63,11 +67,11 @@ ARTIFACT_NAME
|
||||
Before a release:
|
||||
|
||||
1. run the release checklist,
|
||||
2. verify CI is green,
|
||||
2. verify CI is green on a supported Gitea Ubuntu runner,
|
||||
3. verify download links,
|
||||
4. update README and changelog,
|
||||
5. verify release artifacts exclude Codex kit metadata such as `AGENTS.md`, `.codex/`, `blueprint.md`, `blueprint.json`, template workflows, and agent handoff notes unless the user explicitly wants those shipped,
|
||||
6. create a tag,
|
||||
7. create the release.
|
||||
7. create the release through Gitea Actions or the Gitea API.
|
||||
|
||||
Do not create releases unless the user explicitly asks for a release.
|
||||
|
||||
Reference in New Issue
Block a user