Repository navigation
chore: pin sponsord to v0.2.0 - #167
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
Moves the decdn/sponsord pin to the line `0.2` and v0.2.0, from `0.1` and v0.1.0: sponsord_version and sponsord_onramp_version, Compose's two image digests (from the release's signed *-image-digest.txt, verified against the vendored KEYS), the commented exact examples and AGENTS.md's pin paragraph. No env var, metric or KEYS change upstream. sponsord-onramp 0.2.0 refuses an ONRAMP_DECDN_RELEASE below v0.2.0 at startup (its installers run `decdn get` without `-o`, which decdn v0.1.x refuses), so the onramp role now checks that floor in preflight, before installing, instead of failing the /healthz gate after; an exact sponsord_onramp_version below 0.2 is exempt. validation-sponsord covers the refusal. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
thiras
force-pushed
the
chore/sponsord-v0.2
branch
from
October 19, 2026 19:21
61ee27b to
558a8be
Compare
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
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.
Moves the decdn/sponsord pin to the line
0.2and v0.2.0, from0.1and v0.1.0. Stacked on #166 (itself on #165): sponsord-onramp 0.2.0 needs the onramp's decdn pin atv0.2, which #165 moves, so these land in order; GitHub retargets each when its base merges.config.rsenv var, metric, KEYS or release-workflow change in either daemon; the onramp's installers stop adding-o .and take blob URIs (needs decdn ≥ 0.2.0).SPONSORD_IMAGE_DIGESTandSPONSORD_ONRAMP_IMAGE_DIGESTcome from the release's*-image-digest.txt, verified againstansible/roles/sponsord/files/sponsord-release-KEYS.asc; both resolve on ghcr.io.One behavioural addition. sponsord-onramp 0.2.0 refuses an
ONRAMP_DECDN_RELEASEbelowv0.2.0at startup (MIN_DECDN_RELEASE). The onramp role now asserts that floor in preflight, so an operator pinningsponsord_onramp_decdn_release: v0.1gets a message before the install rather than the fatal/healthzgate after it; an exactsponsord_onramp_versionbelow 0.2 is exempt.validation-sponsordgains the refusal case.Verified:
make test-scripts,make lint,make lint-compose,make lint-ansible,make molecule SCENARIOS='validation-sponsord sponsord-onramp sponsord'.After merging all three, release
decdn.node,decdn.publisherand the chart (RELEASING.md).🤖 Generated with Claude Code