chore(ci): deterministic universe pin for ghcr.io/hanzoai/kms#18
Open
zeekay wants to merge 1 commit into
Open
Conversation
The hanzo KMS fork is already a thin wrapper over canonical luxfi/kms
(go.mod imports luxfi/kms v1.11.7) with CI that publishes
ghcr.io/hanzoai/kms via .github/workflows/{build,release}.yml. The live
DOCR one-off (registry.digitalocean.com/hanzo/kms:web-1.11.0) is
superseded — the universe canonical kms deployment already pins the GHCR
image. This change makes the source tree deterministic so a real tag can
be cut:
- go.sum: reconcile luxfi/zap v0.8.1 content hash after an upstream
re-tag (the prior brand-scrub go.sum fix covered luxfi/age + luxfi/kms
but missed zap, breaking `go build` with a checksum mismatch).
- go.mod: correct the stale upstream-pin comment (keys v1.2.0,
kms v1.11.7) to match the require block — comment must not drift.
- VERSION: 2.5.2 -> 2.5.5, the next patch carrying the luxfi/kms v1.11.7
bump, so VERSION, the next git tag, and the published GHCR image all
agree (latest tag was v2.5.4).
- LLM.md: document the release pipeline and the canonical universe pin.
Build green: go build ./cmd/{kmsd,kms,kms-fetch}, go mod verify all pass.
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
2 participants
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
The hanzo KMS fork is already the DRY option (b): a thin wrapper over canonical
luxfi/kms(go.modimportsgithub.com/luxfi/kms v1.11.7), with CI that already publishesghcr.io/hanzoai/kms:.github/workflows/build.yml-> per-commitghcr.io/hanzoai/kmsvia reusablehanzoai/.github/.github/workflows/docker-build.yml@main.github/workflows/release.yml-> on semver tags, multi-archghcr.io/hanzoai/kms:vX.Y.Z+:X.Y.Z+:latest, and dispatcheshanzoai/universeto bump the pinSo no new fork mechanism or CI is needed. The live DOCR one-off (
registry.digitalocean.com/hanzo/kms:web-1.11.0) is already superseded —hanzoai/universeinfra/k8s/kms/deployment.yamlpins the GHCR image, not DOCR.This PR makes the source tree deterministic so a real tag can be cut:
luxfi/zap v0.8.1content hash after an upstream tag re-publish. The prior brand-scrub go.sum fix coveredluxfi/age+luxfi/kmsbut missedzap, sogo buildfailed with a checksum mismatch (SECURITY ERROR). Fixed by recording the authoritative origin hash; the/go.modhash is unchanged (content re-tag, not API change).keys v1.2.0,kms v1.11.7).2.5.2->2.5.5(next patch carrying theluxfi/kms v1.11.7bump; latest tag wasv2.5.4), so VERSION, the next git tag, and the published GHCR image all agree.Verification
Universe pin
After tag
v2.5.5is cut andrelease.ymlpublishes, the universe manifest should pin: