chore: always check yarn lock and dedupe during update #12508
Merged
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.
yarn.lock
needs to be updatedContext: In #12433 we modified the package.json of
@babel/code-frame
but forgot to commit Yarn lock changes. The CI does not bail because the install check is skipped when CI has yarn cache for theyarn.lock
. This PR refines the CI step so that it always check whetheryarn.lock
need to be modified. I catch this issue when my fork fails: https://github.com/JLHwung/babel/runs/1557682750The CI now bails as expected: https://github.com/babel/babel/runs/1557842082
The following commit fixes this error.