repo, signer: Pin securesystemslib better#243
Merged
jku merged 1 commit intotheupdateframework:mainfrom Apr 3, 2024
Merged
Conversation
Securesystemslib is "pre 1.0" so the normal pinning does not really work: the new pinning "~= 0.31.0" should lead to 0.31.1 to be accepted but not 0.32.0.
lukpueh
pushed a commit
to lukpueh/in-toto
that referenced
this pull request
Apr 3, 2024
There are several breaking changes coming up in securesystemslib on its way to 1.0. To not disrupt in-toto users this patch pins securesystemslib to its current minor version. This is similar to what python-tuf and tuf-on-ci do: - theupdateframework/python-tuf#2600 - theupdateframework/tuf-on-ci#243 Signed-off-by: Lukas Puehringer <[email protected]>
Closed
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.
Securesystemslib is "pre 1.0" so the normal pinning does not really work: the new pinning "~= 0.31.0" should lead to 0.31.1 to be accepted but not 0.32.0.