Skip to content

Update helium-swift SDK to 4.3.0#64

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
update-ios-sdk-4.3.0
Open

Update helium-swift SDK to 4.3.0#64
github-actions[bot] wants to merge 1 commit into
mainfrom
update-ios-sdk-4.3.0

Conversation

@github-actions

@github-actions github-actions Bot commented Mar 31, 2026

Copy link
Copy Markdown

Automated update of helium-swift SDK dependency to version 4.3.0.

Changes:

  • Updated podspec dependency version
  • Bumped package.json version (patch increment)

This PR was automatically created by the iOS SDK release workflow.


Note

Medium Risk
Moderate risk because it upgrades a native iOS SDK dependency, which can introduce behavioral or API changes at build/runtime despite minimal code changes here.

Overview
Updates the iOS podspec to depend on Helium 4.3.0 (from 3.1.6).

Bumps the library version in package.json from 3.0.23 to 3.0.24 to publish the dependency update.

Written by Cursor Bugbot for commit 81eb723. This will update automatically on new commits. Configure here.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Comment thread package.json
{
"name": "@tryheliumai/paywall-sdk-react-native",
"version": "3.0.23",
"version": "3.0.24",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Major dependency bump masked as patch version update

Medium Severity

The native Helium CocoaPods dependency jumps from 3.1.6 to 4.3.0 (a major version change), but the npm package version only gets a patch increment (3.0.233.0.24). Consumers using semver ranges like ^3.0.23 will automatically receive this update, which bundles a major native SDK version change. This violates semver expectations — a major dependency upgrade can introduce behavioral changes, even if the wrapper's Swift bridge API remains source-compatible.

Additional Locations (1)
Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant