Repository navigation
chore: simplify CI environment setup - #808
Merged
Merged
Conversation
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.
Summary
Share environment setup between CI and release builds through a local composite action.
pnpm/setup@v3installs the manifest-selected pnpm and Node.js, caches the package store, and requires frozen dependencies. Rust jobs retain their pinned toolchain, separate target directories, and existing cache-save policy.Related Issue
Not applicable.
Verification
An external workflow-comparison harness confirmed that job identities, triggers, gate dependencies, validation commands, deployment steps, and Rust cache settings are preserved. Actionlint validated both workflows, and
pnpm exec oxfmt --checkpassed for the changed YAML and contribution guidance. The pre-pushpnpm lint:tscandpnpm lint:oxlintchecks passed.Not verified locally: execution of the composite action on GitHub-hosted runners, application suites, desktop E2E, or the tag-triggered release workflow. Pull request CI exercises all three check jobs and the gate.