Darkatse c4c2856f17 ci: build portable binaries in their own jobs and keep Rust caches reusable ... The Windows release job built the bundles and then the portable binary, so the portable link sat on the Canary critical path (56 min on 2026-10-08). Build the portable binaries in a separate matrix job; they build their own frontend and, on Canary, restore the desktop release cache of the same platform. The repository cache was at its 10 GB limit and dev had lost every desktop cache: Canary built from scratch (Windows 55 min cold against 36 min warm). The default rust-cache key ignored the matrix, so release and debug builds on one runner shared a key. Give each Canary release build its own key and leave the debug builds uncached. Stable and pull requests no longer cache: caches saved under a tag or a PR ref are not reused by later runs and only evicted dev's. Validation: workflows parse; jobs, steps and publish dependencies checked. Cache budget to confirm after the next Canary runs.		2026-10-09 23:45:27 -04:00
..
codex	feat(ci): include stable release notes in TestFlight context	2026-07-30 16:17:06 -04:00
ISSUE_TEMPLATE	chore(github): add issue templates and modernize cross-platform CI	2026-07-18 20:35:58 -04:00
workflows	ci: build portable binaries in their own jobs and keep Rust caches reusable	2026-10-09 23:45:27 -04:00
dependabot.yml	ci(deps): automate Cargo dependency checks	2026-08-13 22:53:42 -04:00
pull_request_template.md	docs(CONTRIBUTING): create CONTRIBUTING.md	2026-06-23 22:58:18 -04:00