Repository navigation
feat: release Transaction Kit 0.1.0 RC - #1
Merged
Merged
Conversation
- core: cancel()/topUp() wrapping genlayer-js cancelTransaction/topUpFees;
PolicyQuote.verification {verified|mismatch|unavailable} comparing the quote's
fee-config hash against the live fee policy (reconstruction pins the SDK's
12_000bps cap headroom; mismatch fails closed)
- react/vue: blocked state gates approve on mismatch unless allowUnverified;
canCancel/canTopUp + cancel()/topUp() during manageable pending states;
generation guard so late track polls cannot overwrite a cancel outcome
(regression-tested in both adapters; also fixes stale-preset closure in approve)
- tests: core 17, react 15, vue 12 (vue gains its first flow tests)
- README: API table updated
Implemented by Codex (GPT); race fix + headroom pinning notes from review.
Pin the public core package to genlayer-js 2.0.0-rc.1, validate the coordinated workspace version and tarball surface, and add a tag-owned npm publication path. The release script refuses to tag until native CI and the repository-owned npm credential preflight are green.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Delivery context
This PR targets
v0.1-devand contains the complete first Transaction Kit RC cut: the existing fee lifecycle and verification-gate commit plus a dedicated release-preparation layer.The runtime dependency is the already-published immutable
genlayer-js@2.0.0-rc.1artifact from release SHA672631bfff0a21a25d95591a523497f7c46fd01d. There is no open cross-repository PR dependency.Problem and outcome
The three Transaction Kit workspaces were only consumable from generated Git branches and still depended on the moving
genlayer-js#v2-devref. This makes a coordinated, reproducible prerelease impossible.This change prepares and guards the first public RCs:
@genlayer/transaction-kit@0.1.0-rc.1@genlayer/transaction-kit-react@0.1.0-rc.1@genlayer/transaction-kit-vue@0.1.0-rc.1The core package pins
genlayer-js@2.0.0-rc.1exactly, while stable npm tags remain untouched.Implementation and validation
rc, then verifies all registry artifacts and creates a GitHub prerelease.npm audit --omit=devreports zero vulnerabilities.genlayer-js@2.0.0-rc.1.Full E2E is not requested because this repository is not in the protocol deployment closure and the release additions are covered by native package gates.
Release procedure
After merge, both CI and the repository-owned npm credential preflight must be green on the exact
v0.1-devhead. Only then:The script pushes
v0.1.0-rc.1; GitHub Actions performs every npm publication. No local npm credential is used.