Bump defaultCliVersion to 1.7.2 for v1.31.1 admin-tools#10640
Merged
fretz12 merged 1 commit intoJun 10, 2026
Conversation
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.
What changed?
Bumps
defaultCliVersionfrom"1.7.1"to"1.7.2"in.github/actions/build-docker-images/scripts/main.go.This is the version of the
temporalCLI binary downloaded and bundled into the admin-tools Docker image at build time.Why?
Final step of the OSS server v1.31.1 patch. CLI v1.7.2 was just released (temporalio/cli#1088) and bumps
go.temporal.io/server v1.31.0 → v1.31.1, picking up the v1.31.1 security fixes transitively:apache/thrift v0.21.0 → v0.23.0(CVE-2026-41602)golang.org/x/crypto v0.46.0 → v0.52.0(GO-2026-5005..5023)golang.org/x/net v0.48.0 → v0.55.0(GO-2026-5026, etc.)1.26.3 → 1.26.4(stdlib HIGH CVEs)These findings show up in grype scans of
temporaliotest/admin-tools:sha-<latest>because the bundled CLI binary at v1.7.1 was built before our v1.31.1 cherry-picks. Bumping to v1.7.2 clears them.How did you test it?