Repository navigation
pin macula-go v0.29.0, the release that carries A0 - #25
Merged
Merged
Conversation
A caller that a keyed provider refuses sealed_required now reseals to the key in the refusal's signed tbs and is answered, instead of failing on a stale keyless candidate. Builds and verifies the commit beside the tag; the suite passes at the new pin. Co-Authored-By: Claude Code <noreply@anthropic.com>
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.
Refs #24.
Pins macula-go v0.29.0 (
9f84784a773914ccb419eb928f78ff7fe12599e4), the release that carries release A0's reading side (macula-io/macula-go#43).What it buys a user of this package: a call that a keyed provider refuses
sealed_requirednow recovers by resealing to the key carried in the refusal's signed tbs, and is answered, instead of failing on a stale keyless candidate for as long as that candidate lives. A clear client stream that wrote before the refusal replays its writes in order under the sealed reopen.The pin is a tag and the commit beside it, as before; the build resolves the tag and refuses a mismatch. No API, no docs and no version of this package change.
Local before pushing:
npm run build:goresolvedv0.29.0 (9f84784a7739…), the suite passed (68 tests, 3 skipped), andnpm run typecheckwas clean.🤖 Generated with Claude Code