Repository navigation
ci: releases build alongside their checks, from caches kept warm on main - #84
Merged
Merged
Conversation
- the release, macos and linux jobs no longer wait for the checks; the feed job, which publishes the release, waits for them, so a failed check still publishes nothing (the release stays a draft, which releases/latest/download and installed apps never see) - release-cache.yml keeps, on main, the caches a tag's run can read: the Mac's Go build cache and the Rust dependencies of the Mac (universal) and Linux apps, by building what the release builds without signing or bundling; on dependency changes and twice a week, since GitHub drops a cache nobody reads for seven days - the macos and linux jobs restore them (Swatinem/rust-cache, and the Go build cache by prefix), and never write caches no later tag could read CI runs on pull requests only, whose caches no tag sees: every release compiled the app's Rust twice (about 9 minutes) and its Go cold (about 3) after waiting for the checks (about 13). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tag-to-published took about 37 minutes for v0.3.16. Where it went:
macos, 16 minutes, of which about 9 were compiling the app's Rust from scratch twice (Apple silicon 5m 04s, then Intel 4m 07s) and about 3 were cold Go builds.main's caches, so every release started cold.Changes
release,macosandlinuxno longerneedchecks.feed, the job that publishes (--draft=false --latest), needschecksand runs only if they pass. Until then the release is a draft, whichreleases/latest/download/(the install script and the updater feed) never serves. So a failed check still publishes nothing, as before; it just leaves a draft with assets.mainby a newrelease-cache.yml, on dependency changes, Mondays and Thursdays (GitHub evicts a cache unread for 7 days), and on demand:go buildinvocations asmake app-binariesanddaemons, and the Rust deps ofpnpm tauri build --target universal-apple-darwin --no-bundle(same features as the release, no signing or bundling)pnpm tauri build --no-bundle(release profile)Swatinem/rust-cache, the pinci.ymlalready uses, withshared-keyandsave-if: false;actions/cache/restoreby prefix for Go) and never save their own, since no later tag could read them.The release skill describes the new order. Expected: about 15 minutes from tag to published once the caches are warm. Merging this runs
release-cache.ymlonce, since it's in its own path filter.Not done: per-architecture parallel builds or two dmgs, and larger macOS runners.
Checks: actionlint passes on both workflows,
tauri build --no-bundle --targetexists in the app's CLI, and the warm job's Go commands run locally.🤖 Generated with Claude Code