Repository navigation
chore(release): prepare 0.1.0 - #58
Conversation
Bump the package to 0.1.0 and turn the Unreleased changelog section into 0.1.0, with a short lead on the changes most apps need to make. A minor bump rather than 0.0.18: since 0.0.17 the public API changed (payServiceStatus is async and reports isSupported/hasActiveCard, canMakePayments is removed, PaymentResult requires status, the pay buttons take a plain onPress, shippingMethods is ShippingMethod[]). bun install does not rewrite bun.lock for a version-only change, so the workspace version there is updated by hand.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Release entry and package version CHANGELOG.md, package/package.json |
The changelog records checkout status fields, the asynchronous payServiceStatus() result, and the pay buttons’ plain-function onPress signature. The package version changes to 0.1.0. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Other
Possibly related PRs
- gmi-software/react-native-pay#50: Changes checkout availability fields and makes
payServiceStatusasynchronous, which the release entry highlights. - gmi-software/react-native-pay#52: Adds payment-result status and error fields, which relate to the checkout status changes noted in the release entry.
- gmi-software/react-native-pay#53: Changes the pay-button
onPressAPI to accept plain functions, as noted in the release entry.
Suggested reviewers: piotr-graczyk-dev
Merge Risk: 
Minimal · up to 5a0f5
-
The release metadata is ready to merge after normal checks.
Pre-merge checks: 
6
-
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
Full details: Security Check
-
Explanation
No security vulnerability is introduced. The PR changes only release metadata: the package version in
package/package.jsonandbun.lock, plus theCHANGELOG.mdheading and release text. It adds no executable code, dependency, permission, authentication, data-flow, or sink changes. The security check therefore has no medium-, high-, or critical-severity finding.
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.
Comment @coderabbitai help to get the list of available commands.
Summary
@gmisoftware/react-native-payto 0.1.0 (package/package.json, and the workspace version inbun.lock).CHANGELOG.md:## Unreleased→## 0.1.0 — 2026-10-27, with a short lead naming the changes most apps need to make. This section becomes the GitHub Release body (ci: publish releases from CI with npm trusted publishing #57).payServiceStatuswithisSupported/hasActiveCard,canMakePaymentsremoved, requiredPaymentResult.status, plainonPresson the pay buttons,ShippingMethod[].Test plan
bun install --frozen-lockfilepasses with the editedbun.lockpackage/scripts/changelog-section.js 0.1.0(from ci: publish releases from CI with npm trusted publishing #57) extracts the section, about 20 kBorigin/main(34d08a3):bun run typecheck,bun run lint(0 warnings),bun run test:ci(146/146),bun run check:pack(271 files, OK). This PR changes no code.Risk
v0.1.0is pushed after ci: publish releases from CI with npm trusted publishing #57 merges and the npm trusted publisher is configured.Notes
git tag -a v0.1.0 -m v0.1.0 && git push origin v0.1.0.Need help on this PR? Tag
@codesmith-botwith what you need.