feat: auto-maintained arm64 sha256 pin for the kiro-cli install#84
Merged
Conversation
Add a custom.kiro-cli-arm64 datasource (same install manifest, JSONata selecting the aarch64-unknown-linux-gnu headless zip digest), a second match shape on the kiro-cli customManager for the KIRO_CLI_SHA256_ARM64 literal (its `# kiro-cli <version>` trailer is the version anchor, the same trailer model as the golang per-arch sha manager), and a kiro-cli grouping packageRule folding the version and both arch digests into one PR. The web-terminal-kiro and vibekit entrypoints are moving from log-only aarch64 hashes to fail-closed per-arch verification; the grouping rule is load-bearing for them — an ungrouped bump would land version-without-arm64-sha and break every aarch64 boot until the paired update arrived. This config must land before the entrypoint changes. Manifest coverage verified: the latest 40 releases all publish per-arch sha256 for the headless zips. Both manager shapes simulated against both entrypoints (exact matches, no cross-contamination with the existing amd64 pair shape).
cplieger
enabled auto-merge (rebase)
July 16, 2026 19:19
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.
Summary
Renovate config for enforcing the kiro-cli aarch64 zip digest (today only amd64 is enforced; arm64 is logged, not gated):
custom.kiro-cli-arm64datasource — same install manifest, JSONata selects theaarch64-unknown-linux-gnuheadless zip sha256 per release.KIRO_CLI_SHA256_ARM64="…" # kiro-cli <version>inentrypoint.sh; the trailer comment carries the version (golang per-arch sha manager model).kiro-cligrouping packageRule — one PR movesKIRO_CLI_VERSION,KIRO_CLI_SHA256, andKIRO_CLI_SHA256_ARM64together, so neither arch's fail-closed gate can land stale.Landing order
This must merge before the paired web-terminal-kiro / vibekit entrypoint changes (both-arch enforcement). Without this config, their next kiro-cli bump would strand the arm64 literal and fail-closed every aarch64 boot.
Tested
default.jsonvalidates as JSON.