chore: fix dependency versions #82
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
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.
To avoid future hassles like updating the example images for the integration tests in #81, we want less variance in the used dependencies. With the
~=operator, we allow the patch version to be upgraded while the major and minor versions stay the same. This allows us to benefit from security fixes without changing the behaviour and functionality of the used dependencies.The exact behaviour in version changes depends hugely on the versioning practices of the dependency developers.
The tests will only succeed after emerging PR #81. When this PR is merged into the
mainbranch, retrigger just retrigger the tests.