chore(ci): repin x402 images to 2e8a97e#661
Closed
bussyjd wants to merge 1 commit into
Closed
Conversation
Embedded x402 pins lagged at 81a5c52; the frontend bump (df92a23) changed internal/embed afterward, so release.yml's verify-image-pins gate fails on current main. x402 verifier/buyer/controller binaries are byte-identical 81a5c52..a122ff2 (no x402 source changed), so this repins to the 2e8a97e build (images in ghcr) purely to satisfy the gate and tag v0.11.0 off latest main. The auto repin-embedded-pins job is rejected by branch protection (must PR + lint-test).
HananINouman
approved these changes
Jun 23, 2026
Contributor
Author
|
Superseded by 91aa756 |
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
Repin the embedded x402 image pins from
81a5c52→2e8a97ein:internal/embed/infrastructure/base/templates/x402.yaml(x402-verifier, serviceoffer-controller)internal/embed/infrastructure/base/templates/llm.yaml(x402-buyer)Why
release.yml'sverify-image-pinsgate fails on currentmain: the pins point tobuild
81a5c52, butdf92a23(frontend bump) later changedinternal/embed/...,marking the pins stale. This blocks tagging v0.11.0 off latest main.
The automated
repin-embedded-pinsjob indocker-publish-x402.ymlwas supposed toland this bump, but it has failed on every
mainpush withBRANCH_PROTECTION_RULE_VIOLATION("Changes must be made through a pull request.Required status check 'lint-test' is expected.") — the github-actions bot can't
commit directly to protected
main. Hence this manual PR.Validation
2e8a97eexist in ghcr (build job succeeded; only the repin step failed).verify-x402-pins.sh HEADwith these pins reports: "embedded x402 image pins arefresh: 2e8a97e covers all verifier/controller/buyer source between the pin and HEAD."
2e8a97eindex digests).Follow-up (separate)
Fix the auto-repin job so it doesn't need this manual step: either bypass-list the
github-actions bot for the two pin files in the
mainruleset, or have the job opena PR instead of committing to
main.