fix: pass yarn cache inputs to ctcOpen in promote workflow - #2882
Merged
Conversation
The ctcOpen composite action defaults to npm/package-lock.json for dependency caching, but this repo uses yarn. Without explicit inputs, actions/setup-node fails with 'Some specified paths were not resolved' because package-lock.json doesn't exist, cascading into a skipped CTC open and a failed promote job.
soridalac
approved these changes
Aug 19, 2026
1 task
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
2 participants
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
package-manager: yarnandcache-dependency-path: yarn.lockto thectcOpencomposite action in the promote workflowopen-ctc-or-skipjob failure introduced after fix: support package manager retries in VS Code promotion - W-23832274 github-workflows#170 landed — that PR added package-manager inputs toctcOpenbut the defaults (npm/package-lock.json) don't match this repoRoot cause
The
ctcOpenaction runsactions/setup-node@v4withcache: npmandcache-dependency-path: package-lock.jsonby default. Since this repo uses yarn,package-lock.jsondoesn't exist, causing:This cascades: setup-node fails → npm install is skipped → CTC case open is skipped → the status-check step sees
outcome=failure→ job fails.Test plan
latest-rc→latest) and confirmopen-ctc-or-skippasses