refactor(api)!: remove legacy compatibility - #256
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Important Review skippedToo many files! This PR contains 403 files, which is 303 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (8)
📒 Files selected for processing (436)
You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
52dba9e to
1530a42
Compare
Remove scheduled legacy operations, aliases, compatibility fields, and generator shims from the canonical schema. Regenerate and synchronize every language projection from the new contract.\n\nBREAKING CHANGE: deprecated schema APIs and generated compatibility members are no longer exposed.
Remove deprecated Apple and Android entry points, compatibility listeners, receipt aliases, and legacy offer mappings. Keep the canonical StoreKit and Play, Horizon, and Amazon implementations aligned with the regenerated OpenIAP contract.\n\nBREAKING CHANGE: deprecated native package APIs are no longer available.
Remove deprecated aliases, bridges, fallbacks, helpers, and example usage from React Native, Expo, Flutter, Godot, KMP, and MAUI. Keep native payloads and canonical OpenIAP APIs aligned across every framework, including rebuilt Godot runtime artifacts.\n\nBREAKING CHANGE: deprecated framework APIs and legacy wire fallbacks are no longer available.
Replace removed legacy API pages and examples with canonical OpenIAP guidance. Document the coordinated future major versions, migration paths, and the permanent prohibition on outbound IAPKit-to-SDK webhook streams while preserving inbound store webhooks.\n\nBREAKING CHANGE: documentation now targets only the post-compatibility major API surface.
Update repository guidance, generated agent context, and parity audits so removed compatibility APIs cannot return unnoticed. Keep inbound store webhooks documented while rejecting any outbound IAPKit-to-SDK stream.
Prevent clean Expo SDK 54 Android builds from linking the incompatible Worklets CMake output. The example does not import Reanimated or Worklets, so Expo Router can continue treating Reanimated as an optional peer.
563c725 to
90d3cdb
Compare
Summary
Breaking changes
This PR removes APIs and wire fallbacks that were retained through the 2.x/15.x/4.x/9.x/1.x compatibility trains. Consumers must migrate before adopting the coordinated major releases.
Package metadata is intentionally not bumped in this feature PR; stable release workflows own those version changes after merge.
Webhook boundary
Migration
The updated deprecation page maps every removed API to its canonical replacement. Release notes group the common contract changes and package-specific migration requirements under the existing unreleased major train.
Verification
Preview
Open the compressed documentation preview. It shows the rendered July 29 release entry,
Package Releases, and the aligned three-column removal tables. No credentials or customer data are included.