ci: hermetic tests on every push, and a skew job against a released hub

A client that only ever meets the hub it was written with is not
tested against the hubs operators run. The skew job downloads a
released binary and runs the same suite against it.

It needs CHAIN_RELEASE_READ_TOKEN, because a Forgejo job token cannot
read release assets, and says so and fails instead of passing quietly
when the secret is absent.

Signed-off-by: flemming-it <sf@flemming.it>
This commit is contained in:
flemming-it 2026-10-27 02:19:50 +01:00
parent 0db793494d
commit 986377f1df
2 changed files with 107 additions and 0 deletions

View file

@ -134,6 +134,14 @@ tests, and the guard that the `.proto` copies still match both their
recorded hashes and the platform repo. The real-hub suite skips itself
when no binary is there.
`.forgejo/workflows/ci.yml` runs the same two things in CI: the
hermetic suite on every push, and a skew job that downloads a
*released* hub and runs this client against it, because a client has
to keep working against the hub operators actually run. The skew job
needs the repository secret `CHAIN_RELEASE_READ_TOKEN` (a Forgejo job
token cannot read release assets) and fails with that message rather
than passing quietly when the secret is missing.
## License
Apache 2.0. Copyright Dr. Stefan Flemming, Flemming.AI.