Repository navigation
Prepare silo-pkg v3.16.0 dependency maintenance release - #14
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
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 v3.16.0 with go-jose v4.1.9, cpuid v2.4.2 and YAML v3.0.6, publishing the x/net and x/crypto floors already on main. Literal
<<configuration keys now survive YAML save/load. Update both READMEs and the changelog; retain Go 1.27.3, the current upstream minio-go selection and existing compatibility pins.Validation:
make test(lint and full race suite),go mod verify, tidy and diff checks, and govulncheck passed locally. The exact go-jose and coreos OIDC dependency test suites passed under race. The new configuration regression fails with YAML v3.0.5 and passes with v3.0.6. Go, LDAP and VulnCheck CI must pass before release.