Skip to content
zit Check-in [3106100d42]
Login

Check-in [3106100d42]

Overview
Comment:ci: keep the Zig cache and toolchain across runs

The runners are self-hosted but checkout cleaned the workspace, so every step recompiled the same sources into its own binary from nothing; unit tests and e2e were 6 and 4 minutes on the ARM64 critical path, mostly compile. Zig's cache is content-addressed, so it now lives outside the workspace and warms across runs, in both workflows. The toolchain tarball is kept the same way and still verified against the pinned digest every run. Also pins the tag-ignore trigger the previous commit introduced, which the workflow pin test had rejected.

Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 3106100d42d42ddfa5672178bc8680f81bcf2a37b6e262710e7318e98d626bf5
User & Date: dmestas on 2026-09-16 23:09:17.353
Other Links: manifest | tags
Context
2026-09-17
00:08
ci: run on every branch push, still never on a tag

A push trigger naming only a tag filter runs for tag pushes alone, so the tags-ignore alone ran nothing for two commits. branches: ['**'] restores every branch; the pin now allows exactly that form. check-in: c004c81e03 user: dmestas tags: trunk

2026-09-16
23:09
ci: keep the Zig cache and toolchain across runs

The runners are self-hosted but checkout cleaned the workspace, so every step recompiled the same sources into its own binary from nothing; unit tests and e2e were 6 and 4 minutes on the ARM64 critical path, mostly compile. Zig's cache is content-addressed, so it now lives outside the workspace and warms across runs, in both workflows. The toolchain tarball is kept the same way and still verified against the pinned digest every run. Also pins the tag-ignore trigger the previous commit introduced, which the workflow pin test had rejected. check-in: 3106100d42 user: dmestas tags: trunk

22:58
ci: do not run the battery a second time on a tag push

A release tag lands on a commit whose branch push already ran ci, and the tag push ran it again on the same three single-slot runners the release workflow was queueing for. Every branch push still runs; the release workflow, triggered by the tag, gates what it ships. check-in: e9e2ba4431 user: dmestas tags: trunk

Changes