ci: speed up publish workflow#1669
Merged
Merged
Conversation
|
🚅 Deployed to the agentos-pr-1669 environment in agentos
🚅 Environment agentos-pr-1669 in rivet-frontend has no services 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
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.
What changed
Why
The previous publish run spent most of its critical path in work that looked like TypeScript but was actually cold native Rust compilation, plus a WASM cache path that did not restore Cargo target output.
Validation
.github/workflows/publish.yamland.github/workflows/ci.yml.docker buildx build --checkpassed for Linux and Darwin native Dockerfiles.@rivet-dev/agentosdependency ordering restored and native meta builds skippable.~/progress/agent-os/2026-07-08-gh-actions-ci-speed/.Notes
A full local Turbo build is still blocked by an existing local npm shim issue while packing registry packages (
npm@11.18.0path missing), so the real proof should come from the preview publish workflow run.