feat: fail if lockfile isn't up to date #11
Merged
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
phated
suggested changes
Feb 15, 2023
There was a problem hiding this comment.
@TomAFrench This is great! Should it also be added to the test workflows?
|
@phated Whoops! Must have scrolled past that one. Added it now. Also realised I used the wrong flag and we wanted |
phated
approved these changes
Feb 15, 2023
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.
We currently don't have
frozenlocked lockfiles when running CI so it can lead to situations like this where CI passes for a commit where if you build it you'll end up with a completely different lockfile.This PR ensures that CI will fail in these cases.