Toxic/league-of-legends-gui-overhaul
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Process agent kit v1.0.6
All checks were successful
Codex Template Compliance / template-compliance (push) Successful in 26s
Details
Release Dry Run / release-dry-run (push) Successful in 38s
Details
Build / build (push) Successful in 3m49s
Details

Browse Source
This commit is contained in:
ToxicCrzay270
2026-05-19 23:29:44 +02:00
parent 2391a3d094
commit 37a0c78337
6 changed files with 44 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
.codex/project.md
View File

@@ -41,7 +41,9 @@ Build and test verification should run on the Gitea runner with:
.gitea/workflows/build.yml
```
The local machine is not the source of truth for CI results.
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`.
The local machine is not the source of truth for CI results. Local checks are limited to lightweight validation that does not install dependencies or create build artifacts.
## Stack
@@ -80,13 +82,12 @@ No published release process exists yet.
Before a release:
1. run `npm run build`,
2. run `npm test`,
3. run the release checklist,
4. verify CI is green,
5. verify download links when publishing artifacts,
6. update README and changelog,
7. create a tag,
8. create the release.
1. run the release checklist,
2. verify `npm run lint`, `npm test`, `npm run build`, and `npm run audit` are green on a supported Gitea Ubuntu runner,
3. verify download links when publishing artifacts,
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 explicitly requested,
6. create a tag,
7. create the release through Gitea Actions or the Gitea API.
Do not create releases unless the user explicitly asks for a release.