Release github.com/tempoxyz/mpp-go@0.4.0 - #96
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changelog-release/main
branch
7 times, most recently
from
July 28, 2026 00:38
3700819 to
e393214
Compare
github-actions
Bot
force-pushed
the
changelog-release/main
branch
3 times, most recently
from
July 31, 2026 00:25
29be74b to
2bebfa6
Compare
github-actions
Bot
force-pushed
the
changelog-release/main
branch
2 times, most recently
from
August 5, 2026 21:24
73d4503 to
be5c99c
Compare
github.com/tempoxyz/mpp-go@0.3.1github.com/tempoxyz/mpp-go@0.4.0
github-actions
Bot
force-pushed
the
changelog-release/main
branch
6 times, most recently
from
August 11, 2026 15:55
e6abc5e to
55d1061
Compare
github-actions
Bot
force-pushed
the
changelog-release/main
branch
from
August 21, 2026 15:31
55d1061 to
78d1491
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.
This PR was opened by the Changelogs release workflow.
When you're ready to release, merge this PR and the packages will be published.
github.com/tempoxyz/mpp-go@0.4.0Minor Changes
server.Newnow returns(*Mpp, error). (by @erhnysr, #112)Patch Changes
expirescannot be parsed is skipped instead of treated as valid, preventing the client from paying a challenge the server is guaranteed to reject. (by @WinterRong, #88)WWW-Authenticate: Paymentchallenge when payment credential verification fails, allowing clients to retry with the current challenge. (by @pranjalpaliwal, #74)0x(and empty) hex quantity as zero inParseHexUint64, matchingParseHexBigIntso both JSON-RPC integer decoders agree on zero-value forms returned by lenient nodes. (by @salad, #91)decimalsinParseUnits(and thusTransformUnits) instead of panicking on the fractional-part slice. (by @alex, #87)Idempotency-Keyheaders under the canonicalmpp_namespace instead ofmppx_. The key is otherwise byte-identical (Keccak-256 of the signed transaction, or SHA-256 of the canonical relay input), so the previous prefix prevented the relay from deduplicating equivalent canonical and Go submissions of the same transaction or credential retry. Matchessrc/tempo/server/Relay.tsin the canonical mppx implementation. (by @erhnysr, #114)methodortimestampfield when parsing. Both are required base receipt fields per draft-ietf-httpauth-payment §5.3 and the canonical mppx schema; previously an incomplete receipt parsed successfully with an empty method and zero timestamp. (by @erhnysr, #113)WWW-Authenticate: Paymentauth-param lists instead of silently accepting trailing bare parameters or missing separators. (by @markharrison, #92)FormatAuthenticatepath so aChallengefield containing\r\n(e.g.Description,Realm) can no longer split theWWW-Authenticateheader and inject a response.FormatAuthenticateStrictcontinues to reject such values with an error. (by @TLeao, #86)Transportauto-pay after a redirect. ATransportused with a barehttp.Client(noCheckRedirect) had none ofClient.Do's cross-origin redirect protection, so a redirect to an attacker origin could be auto-paid. The Transport now fails closed on any redirect-produced request when no trusted origin is pinned in the context. (by @mattew, #84)EncodeTransferWithMemoinstead of producing invalid Tempo calldata. (by @markharrison, #100)