Skip to content

Expose healthRequest on PurchasesSwiftType#6234

Draft
aboedo wants to merge 1 commit intomainfrom
automation/health-request
Draft

Expose healthRequest on PurchasesSwiftType#6234
aboedo wants to merge 1 commit intomainfrom
automation/health-request

Conversation

@aboedo
Copy link
Copy Markdown
Member

@aboedo aboedo commented Feb 6, 2026

Summary

  • Move healthRequest from InternalPurchasesType to PurchasesSwiftType protocol, making it public
  • Update implementation in Purchases.swift from internal to public
  • Enables hybrid SDKs to call healthRequest through PurchasesHybridCommon

Test plan

  • Verify existing healthRequest unit tests still pass
  • Verify hybrid common layer can compile against updated SDK

🤖 Generated with Claude Code

Move healthRequest from InternalPurchasesType to PurchasesSwiftType so
hybrid SDKs can access it through PurchasesHybridCommon.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@aboedo aboedo self-assigned this Feb 6, 2026
@RevenueCat-Danger-Bot
Copy link
Copy Markdown

1 Error
🚫 Label the PR using one of the change type labels. If you are not sure which label to use, choose pr:other.
Label Description
pr:feat A new feature. Use along with pr:breaking to force a major release.
pr:fix A bug fix. Use along with pr:force_minor to force a minor release.
pr:other Other changes. Catch-all for anything that doesn't fit the above categories. Releases that only contain this label will not be released. Use along with pr:force_patch, or pr:force_minor to force a patch or minor release.
pr:RevenueCatUI Use along any other tag to mark a PR that only contains RevenueCatUI changes
pr:next_release Preparing a new release
pr:dependencies Updating a dependency
pr:phc_dependencies Updating purchases-hybrid-common dependency
pr:changelog_ignore The PR will not be included in the changelog. This label doesn't determine the type of bump of the version and must be combined with pr:feat, pr:fix or pr:other.

Generated by 🚫 Danger

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.

2 participants