🔖 release: mobile@1.1.18

[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.18

Patch Changes

• #802 4aee44e Thanks @cruzdanilo! - 🩹 avoid zero address contract reads

• #801 b6afa4e Thanks @cruzdanilo! - 🥅 report expected errors as sentry warnings

Summary by CodeRabbit

• Chores

  • Released version 1.1.18 as a patch update.

• Documentation

  • Updated changelog to document the patch release version 1.1.18.

[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 the automated release of version 1.1.18 for the @exactly/mobile package. The primary functional change included in this release is an improvement to error reporting, where certain expected errors will now be logged as warnings in Sentry rather than critical errors. This update streamlines the error monitoring process by reducing noise from anticipated events.

Highlights

• Sentry Error Reporting: Expected errors are now reported as Sentry warnings, preventing unnecessary error alerts for anticipated issues.
• Automated Release: This pull request is an automated release for @exactly/mobile version 1.1.18, generated by the Changesets GitHub action.

Changelog

• .changeset/silent-lemons-applaud.md
  • Removed the changeset entry for the mobile package patch release.
• CHANGELOG.md
  • Added a new entry for version 1.1.18 under @exactly/mobile.
  • Included the patch change detail: 'report expected errors as sentry warnings'.
• package.json
  • Incremented the version field from 1.1.17 to 1.1.18.

Activity

• The pull request was automatically opened by the Changesets release GitHub action.
• The author of the change is cruzdanilo.

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]

Caution

Review failed

The pull request is closed.

Walkthrough

Removes a .changeset entry, bumps package.json version from 1.1.17 → 1.1.18, and adds CHANGELOG entries for the 1.1.18 patch (references to PRs included). No runtime or source-code logic changed.

Changes

Cohort / File(s)	Summary
Release metadata .changeset/silent-lemons-applaud.md, CHANGELOG.md, package.json	Removed a changeset entry, added CHANGELOG entries for version 1.1.18 (patch entries referencing PRs #802 and #801), and bumped version in package.json from 1.1.17 to 1.1.18.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• 🔖 release: mobile@1.1.2 #673: Related release metadata edits removing a .changeset and updating CHANGELOG/package.json for a patch release.
• 🔖 release: mobile@1.1.17 #796: Adjacent patch release updates affecting the same release metadata files.
• 🔖 release: server@0.2.56, mobile@1.1.7 #720: Similar changes to .changeset and release metadata for @exactly/mobile.

Suggested reviewers

• dieguezguille
• franm91

🚥 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.18' directly and clearly identifies this as a release PR for @exactly/mobile version 1.1.18, matching the PR's primary purpose of publishing a patch version.

_{✏️ 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 is an automated release for version 1.1.18 of the @exactly/mobile package, updating package.json, CHANGELOG.md, and removing the changeset file. While these are expected changes for a version bump, the PR introduces error classification logic that includes raw error messages in Sentry fingerprints. This poses a risk of leaking Personally Identifiable Information (PII) to Sentry and can lead to poor error grouping. It is recommended to sanitize these messages or use static identifiers for fingerprinting.

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.33%. Comparing base (b6afa4e) to head (5dbef34).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #803      +/-   ##
==========================================
- Coverage   69.34%   69.33%   -0.02%     
==========================================
  Files         208      208              
  Lines        7096     7096              
  Branches     2264     2264              
==========================================
- Hits         4921     4920       -1     
  Misses       1991     1991              
- Partials      184      185       +1     

Flag	Coverage Δ
e2e	52.81% <ø> (-16.49%)	⬇️

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:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.