🔖 new release

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

Patch Changes

• #613 facf0ec Thanks @dieguezguille! - 🐛 handle intercom login errors

Summary by CodeRabbit

Version 1.0.44

• Bug Fixes
  • Improved Intercom login error handling. This patch resolves critical issues that could cause authentication failures when using Intercom integration. The update ensures login errors are handled gracefully, providing users with a more reliable and stable authentication experience throughout their use of Intercom support features.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[cursor]

PR Summary

Release: 1.0.44 (patch)

• Updates package.json version to 1.0.44
• Adds changelog entry for handling Intercom login errors
• Removes processed changeset file /.changeset/cold-planes-stop.md

^{Written by Cursor Bugbot for commit ea1066c. This will update automatically on new commits. Configure here.}

[coderabbitai]

Walkthrough

This PR releases version 1.0.44 of the @exactly/mobile package, which documents and bumps the version for a bugfix that handles Intercom login errors. The changeset entry is removed during the release process.

Changes

Cohort / File(s)	Summary
Release and Versioning .changeset/cold-planes-stop.md, CHANGELOG.md, package.json	Removed changeset entry; added patch entry to CHANGELOG.md documenting bugfix for Intercom login error handling (PR #613); bumped version from 1.0.43 to 1.0.44

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• 🐛 app: handle intercom login errors #613: Implements the Intercom login error handling in src/utils/intercom.ts with try/catch/error reporting logic that this release PR documents and distributes.

Suggested labels

bug

Suggested reviewers

• franm91

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title '🔖 new release' is vague and generic, using non-descriptive terms that don't convey meaningful information about the specific changeset.	Consider using a more specific title that indicates the package and version being released, such as '@exactly/mobile@1.0.44 release' or 'Release @exactly/mobile v1.0.44'.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ 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

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between facf0ec and ea1066c.

📒 Files selected for processing (3)

• .changeset/cold-planes-stop.md
• CHANGELOG.md
• package.json

💤 Files with no reviewable changes (1)

• .changeset/cold-planes-stop.md

🧰 Additional context used

📓 Path-based instructions (2)

**/*.md

📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)

**/*.md: Each markdown file must start with a single top-level heading (# heading 1)
Headings must be sequential (e.g., # -> ## -> ###), do not skip levels
Do not end headings with punctuation (., :, !, ?)
Use a hyphen (-) for unordered list items in markdown
Sub-lists in markdown must be indented with a two-space offset
Always use unordered lists (-) instead of numbered lists (1.) in markdown
All code blocks must be fenced with backticks ( ```) and specify a language identifier
Use sh or `bash` as the language identifier for shell commands in markdown code blocks
All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
All code comments must be lowercase
All lines in markdown files must be no longer than 120 characters
Surround all block-level elements (headings, lists, code blocks) with a single blank line in markdown
Do not add multiple consecutive blank lines in markdown files
No lines should have trailing whitespace in markdown files
Use asterisks (`word`) for italics and double asterisks (`word`) for bold in markdown
Provide descriptive titles for links in markdown instead of generic phrases like 'click here'

Use proper sentence case for user-facing documentation in the docs/ directory

Files:

• CHANGELOG.md

**/*.{mdc,md}

📄 CodeRabbit inference engine (.cursor/rules/style.mdc)

**/*.{mdc,md}: All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose

Files:

• CHANGELOG.md

🧠 Learnings (1)

📚 Learning: 2025-12-23T19:56:56.405Z

Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/dev.mdc:0-0
Timestamp: 2025-12-23T19:56:56.405Z
Learning: Mobile app (exactly/mobile) uses React Native, Expo, Tamagui (UI), Expo Router (navigation), and TanStack Query (state management)

Applied to files:

• package.json

🔇 Additional comments (2)

package.json (1)

3-3: LGTM! Version bump is correct.

The version increment from 1.0.43 to 1.0.44 is appropriate for this patch release that handles Intercom login errors.

CHANGELOG.md (1)

3-8: LGTM! Changelog entry is properly formatted.

The new version 1.0.44 entry correctly documents the bugfix from PR #613, with proper markdown formatting, appropriate heading levels, and a clear description of the change.

---

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

[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 represents an automated patch release for the "@exactly/mobile" package, incrementing its version to "1.0.44". The primary purpose of this release is to deploy a critical bug fix that addresses issues with Intercom login errors. Merging this PR will trigger the automatic publication of the updated package to npm, ensuring users receive the latest improvements and stability enhancements.

Highlights

• New Patch Release: A new patch version, "1.0.44", has been released for the "@exactly/mobile" package.
• Bug Fix Included: This release includes a fix to properly handle Intercom login errors, as detailed in PR 🐛 app: handle intercom login errors #613.
• Automated Release Updates: Standard release files, including "CHANGELOG.md" and "package.json", have been updated, and the corresponding changeset file has been removed as part of the automated release process.

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. ↩

[gemini-code-assist]

Code Review

This pull request is an automated release generated by the Changesets action. It correctly bumps the version of the @exactly/mobile package to 1.0.44, updates the CHANGELOG.md with the latest patch change, and removes the corresponding changeset file. The changes are consistent with a standard release process and look good to merge.

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.52%. Comparing base (5cdd815) to head (ea1066c).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #616      +/-   ##
==========================================
+ Coverage   49.00%   53.52%   +4.52%     
==========================================
  Files          41       48       +7     
  Lines        7100     7776     +676     
  Branches      517      625     +108     
==========================================
+ Hits         3479     4162     +683     
+ Misses       3606     3599       -7     
  Partials       15       15              

Flag	Coverage Δ
github	53.39% <ø> (+4.39%)	⬆️

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.