Updates lockfiles - #943
Merged
Merged
Conversation
f0rmiga
approved these changes
Dec 24, 2022
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
There are a few outdated dependencies. See #928 #925 and a few others.
What is the new behavior?
This PR updates a the relevant lockfiles and tests.
Does this PR introduce a breaking change?
Other information
This PR has highlighted that the process for updating the dependencies in the repo is a little clumsy. Perhaps it's necessary because this repo deals with pinned versions and lockfiles etc, but it does seem like some of the tests are fragile and duplicating logic by testing lockfile behaviour multiple times.