Run CI through the shared plugin action #27

Merged
tiagoagueda merged 1 commit from 1170-shared-ci into main 2026-11-12 09:29:51 +00:00
Owner

Refs postulo/postulo#1170. helloworld is the first plugin to run its CI through the shared action https://source.tiagoagueda.com/Postulo/plugin-ci@v1: ci.yml is checkout plus the action, the audit is its own job with its old name, release.yml runs the release gate through it, and a new weekly.yml runs the audit alone (no full suite on Mondays, no CI on a tag). This run is the action's first: it must show the uv sha check, a cache miss with a full key, the sync, ruff, the catalogue checks and 45 tests.

🤖 Generated with Claude Code

Refs postulo/postulo#1170. helloworld is the first plugin to run its CI through the shared action `https://source.tiagoagueda.com/Postulo/plugin-ci@v1`: `ci.yml` is checkout plus the action, the audit is its own job with its old name, `release.yml` runs the release gate through it, and a new `weekly.yml` runs the audit alone (no full suite on Mondays, no CI on a tag). This run is the action's first: it must show the uv sha check, a cache miss with a full key, the sync, ruff, the catalogue checks and 45 tests. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Run CI through the shared plugin action
All checks were successful
CI / Audit the locked dependencies (pull_request) Successful in 22s
CI / test (pull_request) Successful in 2m51s
19afe22cb4
ci.yml and release.yml were one of seven hand-copied workflows that had drifted
apart, and a uv bump meant editing each of them (postulo/postulo#1170). Every
step now calls Postulo/plugin-ci by its full address at v1, which holds the
pinned uv, uv's cache (new: the core is no longer cloned on every run), the
lint, the catalogue checks and guard, Weblate's gate, the tests, the release
gate and the audit.

What the workflows check is unchanged: the test job still checks out the whole
history and runs lint, extract --check, check, guard, compile, Weblate's gate
on its pull request and pytest; the audit is still its own job; a tag still
runs the release gate alone. Two things move. The weekly schedule leaves
ci.yml for weekly.yml, which runs the audit alone: the test job ran the whole
suite every Monday on an unchanged lock, and this Forgejo fails a job whose
`if` is false rather than skipping it. And the `permissions:` blocks go, as in
the core's workflows: this Forgejo does not support the field and warns.

Refs postulo/postulo#1170

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tiagoagueda deleted branch 1170-shared-ci 2026-11-12 09:29:51 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Postulo/postulo-helloworld!27
No description provided.