Repository navigation
docs: prepare v0.3.0-rc.1 release notes - #400
Merged
Merged
Conversation
Chain payments are listed as unsupported in this release; every shipped configuration keeps them disabled. Co-Authored-By: Claude Opus 5.5 <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
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.
Moves
[Unreleased]to[0.3.0-rc.1] - 2026-10-06(main at a143a8c) and adds Known limitations.Chain payments are excluded. The USDC-on-Sui code is on main, but it is listed as unsupported in this release. Every shipped configuration already sets
[sui] disabled = true, so nothing is built, no keystore is read, andUSDCintents answer503 payments_disabled.TESTpayments are unchanged. The payment schema migrations still ship, because later migrations depend on them.The other limitations listed are the open work in #376, #378, #379 and #382, plus the website verifier still using the pre-v1 scheme.
After merge: push the signed tag
v0.3.0-rc.1on the merge commit. Once tag CI is green, dispatch Prepare signed release with its run ID. A second reviewer must approve therelease-signingenvironment.🤖 Generated with Claude Code