Prepare release: 0.14.2 - #2673
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Prepares the stable
0.14.2release of@cartridge/controllerand@cartridge/connector, consuming@cartridge/controller-wasm@0.10.3from #2672.Self-funded session fallback now reserves 50% gas-price headroom. Regression coverage preserves default sponsored execution, exactly-once confirmation buffering, WASM-owned session estimation, and error propagation. This release changes workspace versions and adds the changelog entry; it introduces no additional runtime changes.
Validation: merged-source quality, TypeScript/unit tests, browser compatibility, and end-to-end checks passed. Release-branch checks must pass before merge; the publish workflow builds and validates packed consumers before publishing both packages to npm
latest.Prompted by: mataleone