Skip to content

Updates inapp module dependency to 0.10.3 #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 9, 2025
Merged

Updates inapp module dependency to 0.10.3 #23

merged 1 commit into from
Jul 9, 2025

Conversation

predatorx7
Copy link
Collaborator

@predatorx7 predatorx7 commented Jul 9, 2025

Summary by CodeRabbit

  • Bug Fixes

    • Resolved parameter key text overflow in the verification review UI.
    • Improved liveliness checks for JavaScript calls sent to the attestor webview.
  • Chores

    • Updated SDK and dependency versions to 0.10.3 across documentation, configuration files, and sample projects.
  • Documentation

    • Refreshed installation and migration guides to reference version 0.10.3.
    • Updated migration links and instructions for the latest release.

Copy link

coderabbitai bot commented Jul 9, 2025

Walkthrough

This update increments the inapp SDK dependency version from 0.10.2 to 0.10.3 across configuration, documentation, and sample files. It also updates migration and installation instructions, changelog, and related links to reference the new version. No changes were made to exported or public entities.

Changes

Files/Groups Change Summary
CHANGELOG.md Added changelog entry for version 0.10.3 with summary of fixes and updates.
InappRnSdk.podspec, android/build.gradle, package.json Updated SDK/dependency version from 0.10.2 to 0.10.3.
README.md, documentation/install-no-framework.md, documentation/migration.md Updated documentation and migration links/instructions to reference version 0.10.3.
samples/example_expo/package.json, samples/example_new_arch/package.json Updated sample dependencies to use version 0.10.3.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Docs
    participant BuildSystem

    Developer->>Docs: Reads updated installation/migration instructions (0.10.3)
    Developer->>BuildSystem: Updates dependencies to 0.10.3 in project files
    BuildSystem-->>Developer: Installs/uses inapp SDK v0.10.3
Loading

Possibly related PRs

  • #16: Updates inapp module dependency from 0.9.1 to 0.9.2 and documentation accordingly, similar to this PR but for a previous version.
  • #19: Updates dependency from 0.9.2 to 0.10.0; related by pattern of version bump and documentation update.

Suggested labels

documentation

Suggested reviewers

  • kryptocodes
  • Sajjad21990

Poem

Hop, hop, a version bump,
From two to three, no major jump!
Docs refreshed, the changelog neat,
Sample files keep their beat.
With every patch, the garden grows—
0.10.3, the carrot shows! 🥕✨


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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (8)
package.json (1)

65-67: Minor: duplicate “.git” suffix in repository URL

Unrelated to this bump but visible in the surrounding context:

"url": "git+https://github.com/reclaimprotocol/reclaim-inapp-reactnative-sdk.git.git"

The double “.git” may confuse tooling that parses the URL. Consider trimming the extra suffix in a follow-up PR.

android/build.gradle (1)

121-121: Centralise library version to avoid drift

Great on updating to 0.10.3. To prevent future mismatches (Gradle vs Cocoapods vs JS), you may want to expose a single INAPP_SDK_VERSION Gradle property and reference it here and in ext, mirroring what you already do for Kotlin.

samples/example_expo/package.json (1)

45-45: Version pinned – differs from caret in other sample

This sample pins the exact SDK version, whereas example_new_arch uses a caret. Pick one approach for consistency (see comment in the other sample).

README.md (1)

139-147: Consider preserving the 0.10.2 migration link or explicitly stating it is unchanged.

Dropping the 0.10.2 bullet removes an otherwise-useful reference for teams that have not yet upgraded from 0.10.2. Either keep the historical link or add a short note that 0.10.3 contains the same steps as 0.10.2.

CHANGELOG.md (1)

1-6: Polish wording & consistency in the new 0.10.3 entry.

Minor copy tweaks keep the changelog professional and consistent with previous sections:

- * Fix param key text overflow verification review
- * Add liveliness checks of javascript calls sent to attestor webview
- * Updates inapp module dependency to 0.10.3
+* Fix parameter-key text overflow in the verification-review UI  
+* Add liveness checks for JavaScript calls sent to the attestor web-view  
+* Update in-app module dependency to 0.10.3

Notes

  1. “parameter-key”, “verification-review UI”, and “in-app” match earlier wording.
  2. “liveness” (vs. liveliness) is the industry term.
  3. Trailing periods omitted to stay consistent with other versions.
documentation/migration.md (1)

5-39: Grammar and spelling fixes for repeated advisory sentence.

The same sentence appears in multiple sections; it reads awkwardly and has a typo (“overriden”). Suggested replacement (apply everywhere this sentence occurs):

-Make sure if you are using the latest versions of `ReclaimInAppSdk` cocoapod if you have overriden this dependency in your `Podfile`.
+If you override this dependency in your `Podfile`, ensure you are using the latest version of the `ReclaimInAppSdk` CocoaPod.

This:

• Removes the double-conditional “make sure if”.
• Fixes “overriden” → “overridden”.
• Capitalises “CocoaPod”.

documentation/install-no-framework.md (2)

137-146: Minor style tweaks for pod declarations.

  1. Add a blank line before code-blocks to satisfy markdownlint rule MD032 (lists & blocks).
  2. Keep the code fences on their own lines for readability:
-##### From a specific tag
-
-```ruby
-pod 'ReclaimInAppSdk', :git => 'https://github.com/reclaimprotocol/reclaim-inapp-ios-sdk.git', :tag => '0.10.3'
-```
+##### From a specific tag
+
+```ruby
+pod 'ReclaimInAppSdk', :git => 'https://github.com/reclaimprotocol/reclaim-inapp-ios-sdk.git', :tag => '0.10.3'
+```

This silences MD032 / MD034 warnings and keeps formatting consistent with other blocks.


181-184: Duplicate pod declaration – ensure single source of truth.

The example Podfile now contains two identical pod 'ReclaimInAppSdk', '~> 0.10.3' lines (one earlier in the Overriding SDK dependency section and one in the sample target). Keeping both may lead to merge-conflict noise. Consider keeping only the one inside the sample target block.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 16d6e04 and d400b75.

📒 Files selected for processing (9)
  • CHANGELOG.md (1 hunks)
  • InappRnSdk.podspec (1 hunks)
  • README.md (1 hunks)
  • android/build.gradle (1 hunks)
  • documentation/install-no-framework.md (2 hunks)
  • documentation/migration.md (3 hunks)
  • package.json (1 hunks)
  • samples/example_expo/package.json (1 hunks)
  • samples/example_new_arch/package.json (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[grammar] ~1-~1: Use correct spacing
Context: ## 0.10.3 * Fix param key text overflow verificatio...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~3-~3: There might be a mistake here.
Context: ...ix param key text overflow verification review * Add liveliness checks of javascript c...

(QB_NEW_EN_OTHER)


[grammar] ~4-~4: Use proper capitalization
Context: ...ation review * Add liveliness checks of javascript calls sent to attestor webview * Update...

(QB_NEW_EN_OTHER_ERROR_IDS_6)


[grammar] ~4-~4: There might be a mistake here.
Context: ...ks of javascript calls sent to attestor webview * Updates inapp module dependency to 0....

(QB_NEW_EN_OTHER)


[grammar] ~5-~5: There might be a problem here.
Context: ...script calls sent to attestor webview * Updates inapp module dependency to 0.10.3 ## 0....

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~5-~5: There might be a problem here.
Context: ...ew * Updates inapp module dependency to 0.10.3 ## 0.10.2 * Add humanized summary of values shown i...

(QB_NEW_EN_MERGED_MATCH)

documentation/migration.md

[grammar] ~7-~7: There might be a problem here.
Context: ...running pod update ReclaimInAppSdk. - Refer: https://github.com/reclaimprotocol/reclaim-inapp-reactnative-sdk/blob/main/README.md#ios-setup ## 0.9.2 - Make sure if you are using the latest v...

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~13-~13: There might be a problem here.
Context: ...running pod update ReclaimInAppSdk. - Refer: https://github.com/reclaimprotocol/reclaim-inapp-reactnative-sdk/blob/main/README.md#ios-setup ## 0.9.1 - Make sure if you are using the latest v...

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~19-~19: There might be a problem here.
Context: ...running pod update ReclaimInAppSdk. - Refer: https://github.com/reclaimprotocol/reclaim-inapp-reactnative-sdk/blob/main/README.md#ios-setup ## 0.9.0 - Make sure if you are using the latest v...

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~25-~25: There might be a problem here.
Context: ...running pod update ReclaimInAppSdk. - Refer: https://github.com/reclaimprotocol/reclaim-inapp-reactnative-sdk/blob/main/README.md#ios-setup ## 0.8.3 - Make sure if you are using the latest v...

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~31-~31: There might be a problem here.
Context: ...running pod update ReclaimInAppSdk. - Refer: https://github.com/reclaimprotocol/reclaim-inapp-reactnative-sdk/blob/main/README.md#ios-setup ## 0.7.3 ### iOS - Make sure if you are using the latest v...

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~155-~155: Use articles correctly
Context: ...re if you are using the 0.2.0 version of ReclaimInAppSdk cocoapod if you have ...

(QB_NEW_EN_OTHER_ERROR_IDS_11)


[grammar] ~155-~155: Ensure spelling is correct
Context: ... ReclaimInAppSdk cocoapod if you have overriden this dependency in your Podfile. Late...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

documentation/install-no-framework.md

[grammar] ~142-142: Use correct spacing
Context: ... '
> 0.10.3' ##### From a specific tag ruby pod 'ReclaimInAppSdk', :git => 'https://github.com/reclaimprotocol/reclaim-inapp-ios-sdk.git', :tag => '0.10.3' ##### From git HEAD ruby pod 'ReclaimInAp...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🪛 markdownlint-cli2 (0.17.2)
documentation/migration.md

7-7: Bare URL used

(MD034, no-bare-urls)


13-13: Bare URL used

(MD034, no-bare-urls)


19-19: Bare URL used

(MD034, no-bare-urls)


25-25: Bare URL used

(MD034, no-bare-urls)


31-31: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (3)
InappRnSdk.podspec (1)

20-20: Pod dependency bumped – verify CocoaPods repo update

The switch to ~> 0.10.3 looks correct. Please ensure the 0.10.3 pod has already been pushed to the private/public spec repo; otherwise pod install will fail for fresh check-outs.

package.json (1)

3-3: SDK version bump acknowledged

Version updated to 0.10.3. LGTM provided CHANGELOG and git tag are in place.

documentation/migration.md (1)

155-156: Out-of-date version reference inside the 0.2.1 iOS note.

The line still tells users to “make sure if you are using the 0.2.0 version” while the surrounding docs promote 0.10.3. Update the referenced version (or drop it) to avoid confusion.

@@ -11,7 +11,7 @@
"test": "jest"
},
"dependencies": {
"@reclaimprotocol/inapp-rn-sdk": "^0.10.2",
"@reclaimprotocol/inapp-rn-sdk": "^0.10.3",
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Align version-range strategy across sample apps

This sample uses a caret (^0.10.3) while samples/example_expo/package.json pins the exact version (0.10.3). Mixing range strategies makes it harder to reason about which SDK revision is actually installed when developers switch between the two demos.

Consider pinning the version here as well for reproducible installs, or switch both samples to a consistent range spec—either way, pick one strategy and stick to it.

-    "@reclaimprotocol/inapp-rn-sdk": "^0.10.3",
+    "@reclaimprotocol/inapp-rn-sdk": "0.10.3",

Run the script below to spot any other mismatched specs:


🏁 Script executed:

#!/bin/bash
rg --no-heading -n '"@reclaimprotocol/inapp-rn-sdk":' samples | sort

Length of output: 242


Pin SDK version in example_new_arch for consistency

To keep installs reproducible and avoid confusion between demos, both sample apps should use the same version-range strategy for @reclaimprotocol/inapp-rn-sdk. The example_expo app pins the SDK to "0.10.3", so we should do the same in example_new_arch.

Affected file:

  • samples/example_new_arch/package.json (line 14)

Suggested change:

-    "@reclaimprotocol/inapp-rn-sdk": "^0.10.3",
+    "@reclaimprotocol/inapp-rn-sdk": "0.10.3",

Verification output:

samples/example_expo/package.json:45:    "@reclaimprotocol/inapp-rn-sdk": "0.10.3"
samples/example_new_arch/package.json:14:    "@reclaimprotocol/inapp-rn-sdk": "^0.10.3",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"@reclaimprotocol/inapp-rn-sdk": "^0.10.3",
"@reclaimprotocol/inapp-rn-sdk": "0.10.3",
🤖 Prompt for AI Agents
In samples/example_new_arch/package.json at line 14, the version of
@reclaimprotocol/inapp-rn-sdk is specified with a caret (^0.10.3), which allows
minor version upgrades. To ensure consistency and reproducible installs with the
example_expo app, change the version to be pinned exactly to "0.10.3" by
removing the caret prefix.

@predatorx7 predatorx7 merged commit 83b0417 into main Jul 9, 2025
1 check passed
@predatorx7 predatorx7 deleted the pre-0.10.3 branch July 9, 2025 20:16
@coderabbitai coderabbitai bot mentioned this pull request Aug 13, 2025
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