Sync yarn lock #1165
Merged
Sync yarn lock #1165
Conversation
This file contains 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
andrew-nowak
approved these changes
Jun 14, 2024
|
Seen on PROD (merged by @rhystmills 6 minutes and 22 seconds ago) Please check your changes! |
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.
What does this change?
The Snyk action wasn't working after my last PR - it was hard to tell the cause from the logs in GitHub because they were huge. After downloading the raw logs, it seems that the
package.jsonandyarn.lockwere out of sync.This PR turns off the
DEBUGoption in the workflow, and synchronises the lock file withpackage.json.How to test
Deploy to CODE, if you're feeling diligent! (I'm doing so now)