Update payment compatibility dependencies together - #24
Merged
Merged
Conversation
ty-everett
marked this pull request as ready for review
September 24, 2026 20:57
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.
Updates SDK 2.8.5, authentication middleware 2.2.8 and payment middleware 2.1.8 together. Received payment headers pass canonical authentication/payment validation without secondary middleware size/count rejection. The HTTP route owns admission; shared SQL sessions, nonce claims and payment replay claims remain unchanged.
No application BRC100 calls, signed wire encodings, prices or wallet records change. Reviewed lock changes are confined to these three packages and the required SDK peer floor.
Validation: frozen install, tests, typecheck, lint, frontend/server builds and production audit (zero vulnerabilities) pass. All three published packages match protected release 36052862859. Fresh native purchase, reread and receipt-integrity acceptance remain required after guarded promotion.