fix: dependency tree #615
Merged
fix: dependency tree #615
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: Carlos A Becker <caarlos0@users.noreply.github.com>
pull-request-size
bot
added
the
size/L
Codecov Report
@@ Coverage Diff @@
## main #615 +/- ##
=======================================
Coverage 70.48% 70.48%
=======================================
Files 21 21
Lines 3168 3168
=======================================
Hits 2233 2233
Misses 717 717
Partials 218 218 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
unfortunately, we need to lock go-crypto to that particular version in order to avoid breaking signing in some centos/rhel versions.
make it super clear in the go.mod file to avoid future mistakes, hopefully.
we need to find a good future plan for it though, even if it is specifically not supporting some rpm versions - if I understood it correctly, its actually a bug on a specific rpm version.