Prepare v3.14.0 with current Go dependencies and SDK fixes - #7
Merged
Merged
Conversation
Signed-off-by: Feng Ruohang <rh@vonng.com>
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
1 participant
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.
Prepare silo-pkg v3.14.0 with the upstream minio-go listing checksum/restore-status fix and the current Go x/crypto, x/net, x/oauth2, x/sys and x/text releases. Preserve the Go 1.26 compatibility floor and document the existing password authorization changes that consumers will receive in this release. Update CI to govulncheck 1.8.0.
Validation:
make test(lint and complete race suite), Go 1.26.8 race suite, and Linux/amd64 govulncheck passed. No reachable or imported-package vulnerability was reported; one module-only advisory remains in unused code. No intentional performance change.