[Chore] Speed up frontend CI dependency setup - #2
Draft
openroomote-bruno[bot] wants to merge 1 commit into
Draft
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
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.
What changed
Make the shared frontend CI setup reuse exact dependency caches keyed by the
bun.lockhash, and skipbun installwhen that exact cache is restored.Why this change was made
Frontend lint, type-check, and test jobs all repeat dependency setup. The existing weekly cache was restored but still followed by an unconditional install, leaving the largest safe cache win unused.
Impact
Most frontend CI jobs should avoid dependency resolution and package installation on exact cache hits, while cache misses and fallback restores still run
bun install --frozen-lockfile. This preserves correctness for changed lockfiles and keeps the cache-generator's unpatched dependency invariant intact.Expected savings are roughly the duration of a Bun dependency install per frontend job on exact cache hits, typically tens of seconds to a few minutes depending on runner and cache state. This deliberately does not change test sharding, runner sizes, or workflow boundaries; those are higher-risk optimizations that need timing data and separate validation.
Validation was limited to
git diff --checkand static inspection becauseactionlint,yq, and a configured YAML parser were unavailable in the sandbox.