Prepare September mcli release with silo-pkg v3.14.0 and current Go dependencies - #42
Merged
Conversation
…ependencies Signed-off-by: Feng Ruohang <rh@vonng.com>
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 the September 13 mcli release with the published silo-pkg v3.14.0, upstream minio-go commit 60bd07042d49, and the current Go official x/* dependencies. Refresh the UBI certificate image and run integration tests against the latest published SILO Server with its pinned archive checksum. Keep Go 1.27.1 and the documented go-systemd NetBSD portability exception.
Local validation: make verifiers (vet/lint, credits, branding, release-state/signature/attestation checks) passed; Linux/amd64 govulncheck reports no reachable or imported-package vulnerabilities. The complete
go test -race -tags kqueue ./...suite also passed. The four release-gating workflows must also pass on the merged main commit before the signed release tag is created.