fix: pass yarn cache inputs to ctcClose in promote workflow - #2883
Merged
Conversation
Same issue as the ctcOpen fix — ctcClose.yml also defaults to npm/package-lock.json caching, which fails because this repo uses yarn.
soridalac
approved these changes
Aug 19, 2026
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 bothctcCloseSuccessandctcCloseFailjobsctcClose.ymlworkflow defaults to npm/package-lock.json caching which doesn't exist in this repoContext
The promotions themselves complete fine (npm, docker, oclif/S3), but the CTC close step fails afterward because of the same missing lockfile issue. The promote workflow still shows as failed even though the actual promotion succeeded.
Test plan
ctcCloseSuccesspasses