Skip to content

[AUTOMATIC BUMP] Updates purchases-hybrid-common to 18.34.0 - #1936

Merged
AlvaroBrey merged 3 commits into
mainfrom
bump-phc/18.34.0
Sep 3, 2026
Merged

[AUTOMATIC BUMP] Updates purchases-hybrid-common to 18.34.0#1936
AlvaroBrey merged 3 commits into
mainfrom
bump-phc/18.34.0

Conversation

@RCGitBot

@RCGitBot RCGitBot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

This is an automatic bump.

Updates purchases-hybrid-common to 18.34.0


Note

Medium Risk
No local bridge code changes, but the bump swaps the native/JS purchase SDK stack and can affect billing, paywalls, and Galaxy store behavior from upstream hybrid-common releases.

Overview
Automatic dependency bump from 18.33.1 to 18.34.0 for RevenueCat hybrid-common artifacts across the monorepo.

Native: iOS CocoaPods pins update in RNPurchases.podspec (PurchasesHybridCommon) and RNPaywalls.podspec (PurchasesHybridCommonUI). Android Gradle updates purchases-hybrid-common, purchases-hybrid-common-ui, and purchases-hybrid-common-store-galaxy in the core, UI, and Galaxy packages.

JS: Root and workspace package.json files move @revenuecat/purchases-typescript-internal (and root @revenuecat/purchases-js-hybrid-mappings) to 18.34.0; yarn.lock reflects that and pulls @revenuecat/purchases-js 1.55.0 (from 1.54.0) via the hybrid-mappings dependency.

Example app: examples/purchaseTesterTypescript/ios/Podfile.lock is refreshed so local pods resolve PurchasesHybridCommon / PurchasesHybridCommonUI at 18.34.0 (still on RevenueCat 5.87.1).

Reviewed by Cursor Bugbot for commit 6d1c9af. Bugbot is set up for automated code reviews on this repo. Configure here.

@RCGitBot
RCGitBot requested a review from a team as a code owner September 3, 2026 07:04
@AlvaroBrey
AlvaroBrey merged commit 046b4e4 into main Sep 3, 2026
12 checks passed
@AlvaroBrey
AlvaroBrey deleted the bump-phc/18.34.0 branch September 3, 2026 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants