fix(security): the self-fetch authenticates, and the ledger names 0.1.15 - #83
Merged
Conversation
The called-workflow source fetch ran anonymously because the repository is public -- which held until GitHub's unauthenticated fetch path failed every consumer for 77 minutes and recovered on its own (#77). The fetch now carries the ambient token in the temp repository's local config, keeping the retry-and-fallback ladder as defense in depth. The release ledger gains the 0.1.15 heading the advisory sweep flagged (#79), describing what the tag actually shipped. Claude-Session: https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF
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.
Closes #77: the
private-security-bundle-freesource fetch carries the ambientgithub.token(basic auth header in the temp repo's local config, never on a command line) — the 2026-08-31 outage hit only the unauthenticated fetch path while authenticated fetches of the same pin succeeded; retries + v0 fallback stay as depth.Closes #79: the release ledger gains the
[0.1.15] - 2026-08-31heading (docker-build.yml, security-bundle resilience fixes, pin-registry sync) — the only finding of the advisory sweep.validate_all --tier core: OK.
https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF