🔖 release: mobile@1.1.2

[cruzdanilo]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@exactly/mobile@1.1.2

Patch Changes

• 665e6c3 Thanks @franm91! - ♻️ use new kyc flow

• #669 1aa1fe6 Thanks @cruzdanilo! - 🧵 fix onesignal prompt persistence race condition

• #672 c6a1241 Thanks @dieguezguille! - 🐛 allow kyc on account deploy

[gemini-code-assist]

Summary of Changes

Hello @cruzdanilo, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request facilitates an automated patch release for the @exactly/mobile package. Its primary purpose is to publish version 1.1.2 to npm, incorporating a specific bug fix related to allowing KYC during account deployment. The changes reflect standard release procedures, updating version numbers and changelog entries.

Highlights

• Automated Release: This pull request is an automated release for the @exactly/mobile package, bumping its version to 1.1.2.
• Bug Fix Included: The release incorporates a patch change that allows KYC (Know Your Customer) during account deployment, addressing an issue identified in PR 🐛 app: allow kyc on account deploy #672.
• Version Updates: The package.json file has been updated to reflect the new version 1.1.2, and the CHANGELOG.md has been augmented with the details of this patch release.
• Changeset Removal: The temporary changeset file .changeset/lucky-fans-tease.md has been removed, indicating that its changes have been successfully integrated into the release.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Warning

Rate limit exceeded

@cruzdanilo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 18 minutes and 12 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

Removes a changeset entry, adds a 1.1.2 patch section to CHANGELOG.md documenting three patch entries (commit 665e6c3 and PRs #669, #672), and bumps package.json from 1.1.1 to 1.1.2. No API or exported declarations changed.

Changes

Cohort / File(s)	Summary
Release Version Bump package.json	Version updated from 1.1.1 to 1.1.2.
Release Management .changeset/lucky-fans-tease.md	Deleted/cleared changeset entry (removed patch bump entry for @exactly/mobile).
Changelog Update CHANGELOG.md	Added 1.1.2 patch release section containing entries: commit 665e6c3 (♻️ use new kyc flow) and PRs #669 (fix onesignal prompt persistence race condition) and #672 (allow kyc on account deploy).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• 🔖 release: mobile@1.1.1, server@0.2.50 #662: Related release changes affecting changeset entries, CHANGELOG.md, and package versioning.

Suggested reviewers

• franm91
• dieguezguille

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title '🔖 release: mobile@1.1.2' clearly summarizes the main change—a release of the @exactly/mobile package version 1.1.2.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-release/main

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[gemini-code-assist]

Code Review

This pull request appears to be an automated release update for @exactly/mobile@1.1.2. The changes include removing the corresponding changeset file, updating the CHANGELOG.md with the new patch version and its description, and incrementing the version number in package.json. These changes are standard for a release process and do not introduce any functional or logical modifications to the codebase. No specific code review comments are necessary.

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.66%. Comparing base (63971d3) to head (907ade0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #673      +/-   ##
==========================================
+ Coverage   61.35%   63.66%   +2.31%     
==========================================
  Files         169      169              
  Lines        5240     5882     +642     
  Branches     1481     1753     +272     
==========================================
+ Hits         3215     3745     +530     
- Misses       1865     1964      +99     
- Partials      160      173      +13     

Flag	Coverage Δ
e2e	62.73% <ø> (+2.52%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Around line 3-7: Update the changelog entry for the "## 1.1.2" release by
lowercasing the subheading "### Patch Changes" to "### patch changes" and
rewriting the list item that starts with "- [`#672`] [`c6a1241`] Thanks
[`@dieguezguille`]! - 🐛 allow kyc on account deploy" so its prose is lowercase
and wrapped to <=120 characters per line (preserve PR/commit/author tokens and
emoji, only change prose casing and line breaks).

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Lowercase and wrap the 1.1.2 changelog entry.

The new heading and list item use capitalized prose and exceed the 120‑character line limit. Please lowercase and wrap the entry.

✏️ Proposed fix

 ## 1.1.2
 
-### Patch Changes
+### patch changes
 
-- [`#672`](https://github.com/exactly/exa/pull/672) [`c6a1241`](https://github.com/exactly/exa/commit/c6a1241d59f04af46d2c31c3ad70baa17de9dd8d) Thanks [`@dieguezguille`](https://github.com/dieguezguille)! - 🐛 allow kyc on account deploy
+- [`#672`](https://github.com/exactly/exa/pull/672)
+  [`c6a1241`](https://github.com/exactly/exa/commit/c6a1241d59f04af46d2c31c3ad70baa17de9dd8d)
+  thanks [`@dieguezguille`](https://github.com/dieguezguille)!
+  🐛 allow kyc on account deploy

As per coding guidelines.

📝 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

	## 1.1.2
	### Patch Changes
	- [#672](https://github.com/exactly/exa/pull/672) [`c6a1241`](https://github.com/exactly/exa/commit/c6a1241d59f04af46d2c31c3ad70baa17de9dd8d) Thanks [@dieguezguille](https://github.com/dieguezguille)! - 🐛 allow kyc on account deploy
	## 1.1.2
	### patch changes
	- [`#672`](https://github.com/exactly/exa/pull/672)
	[`c6a1241`](https://github.com/exactly/exa/commit/c6a1241d59f04af46d2c31c3ad70baa17de9dd8d)
	thanks [`@dieguezguille`](https://github.com/dieguezguille)!
	🐛 allow kyc on account deploy

🤖 Prompt for AI Agents

In `@CHANGELOG.md` around lines 3 - 7, Update the changelog entry for the "##
1.1.2" release by lowercasing the subheading "### Patch Changes" to "### patch
changes" and rewriting the list item that starts with "- [`#672`] [`c6a1241`]
Thanks [`@dieguezguille`]! - 🐛 allow kyc on account deploy" so its prose is
lowercase and wrapped to <=120 characters per line (preserve PR/commit/author
tokens and emoji, only change prose casing and line breaks).