Downgrade go-cose to v1.1.0 #2251
Closed
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
Signed-off-by: Tristan Duncombe [email protected] Signed-off-by: Tristan Duncombe <[email protected]>
Signed-off-by: Tristan Duncombe <[email protected]>
|
@microsoft-github-policy-service agree |
Signed-off-by: Tristan Duncombe <[email protected]>
|
That should resolve the issue (I hope) :) Pretty new to Go, so let me know if there are any issues! |
Signed-off-by: Tristan Duncombe <[email protected]>
|
@tristanduncombe Hi! This issue should be addressed by #2260, which we'll likely merge in the next day or so. Let us know if there are any issues with that! |
|
#2260 addressed this issue. |
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.
Go-cose v1.2.0 has been removed see veraison/go-cose#153
This package requiring this version limits other projects, hence, downgrading should resolve this issue (see #2216 and #2162), I've followed @andrew-lawson-tumelo 's suggestion for v1.1.0.
Hopefully, I've done this correctly!