🔖 release: server@0.2.56, mobile@1.1.7

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

Patch Changes

• #719 46f385b Thanks @cruzdanilo! - 🐛 pad repay assets to avoid dust

• #719 62756c2 Thanks @cruzdanilo! - 🚸 navigate successful repay to activity

• 86bf361 Thanks @cruzdanilo! - 🥅 handle error when reporting to sentry

• c9984a3 Thanks @cruzdanilo! - ⚡️ cache credential in query client

• Updated dependencies [9ac36f0, da675ee]:

  • @exactly/server@0.2.56

@exactly/server@0.2.56

Patch Changes

• 9ac36f0 Thanks @cruzdanilo! - 🗑️ deprecate passkey metadata api

• #723 da675ee Thanks @mainqueg! - ✨ add limits to ramp provider response

Summary by CodeRabbit

• New Releases

  • Version 1.1.7 released with multiple improvements and fixes
  • Version 0.2.56 released for backend services

• Bug Fixes

  • Improved asset handling in repay operations
  • Enhanced error handling for monitoring
  • Optimized credential caching
  • Fixed navigation after successful repayment

• Improvements

  • Added rate limits to provider responses

• Deprecations

  • Passkey metadata API deprecated

[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 is an automated release PR for the @exactly/mobile package, bumping its version to 1.1.7. It incorporates two patch changes: one addressing an issue with repay asset padding to avoid dust, and another improving user experience by navigating to the activity screen after a successful repay.

Highlights

• Repay Assets Padding: Implemented padding for repay assets to prevent 'dust' issues, ensuring more accurate and complete transactions.
• Repay Navigation Improvement: Enhanced user experience by automatically navigating to the activity screen upon a successful repay operation.

Changelog

• .changeset/fair-cooks-hammer.md
  • Removed the changeset file related to padding repay assets, as its changes have been incorporated into the release.
• .changeset/gentle-ducks-repay.md
  • Removed the changeset file related to navigating to activity after repay, as its changes have been incorporated into the release.
• CHANGELOG.md
  • Added new entries for version 1.1.7, detailing the two patch changes: padding repay assets to avoid dust and navigating to the activity screen after a successful repay.
• package.json
  • Updated the package version from 1.1.6 to 1.1.7.

Activity

• This pull request was automatically generated by the Changesets release GitHub action.
• It is currently awaiting merge to trigger the automatic publishing of @exactly/mobile@1.1.7 to npm.
• The PR will be updated automatically if more changesets are added to the main branch.

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 multiple .changeset files, adds a new 1.1.7 entry to CHANGELOG.md, bumps root package.json version to 1.1.7 and updates its @exactly/server dependency to workspace:^0.2.56, and bumps server/package.json to 0.2.56 with an added server/CHANGELOG.md entry.

Changes

Cohort / File(s)	Summary
Changeset removals .changeset/fair-cooks-hammer.md, .changeset/gentle-ducks-repay.md, .changeset/giant-hats-count.md, .changeset/pink-moles-camp.md, .changeset/wide-brooms-heal.md	Deleted several .changeset files that previously described patch notes for @exactly/mobile and @exactly/server. No code or API changes.
Root release metadata package.json, CHANGELOG.md	Bumped root version 1.1.6 → 1.1.7; updated dependencies.@exactly/server to workspace:^0.2.56; inserted 1.1.7 section into CHANGELOG.md.
Server release metadata server/package.json, server/CHANGELOG.md	Bumped server version 0.2.55 → 0.2.56 and added corresponding server/CHANGELOG.md entry.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• 🔖 release: mobile@1.1.6, server@0.2.55 #707: Related release bookkeeping advancing package versions and removing changeset metadata for the same server/root release flow.
• 🔖 new release #605: Release-related changes that delete .changeset entries and update changelogs/package versions.
• 🔖 release: server@0.2.53, mobile@1.1.5 #697: Patch release updates touching changelogs and removing changeset files for mobile/server metadata.

Suggested reviewers

• nfmelendez

🚥 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 accurately describes the pull request, which is a release PR that bumps versions for server@0.2.56 and mobile@1.1.7, matching the changesets and version updates in the included files.

_{✏️ 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.}

[gemini-code-assist]

Code Review

This pull request is an automated release for version 1.1.7 of the @exactly/mobile package, generated by the Changesets action. The changes include updating the package.json version, generating the CHANGELOG.md with the latest patch changes, and removing the corresponding changeset files. The changes are correct and consistent with the release process. I see no issues.

[devin-ai-integration]

✅ Devin Review: No Issues Found

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

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.12%. Comparing base (da675ee) to head (9736dfd).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #720   +/-   ##
=======================================
  Coverage   68.12%   68.12%           
=======================================
  Files         206      206           
  Lines        6780     6780           
  Branches     2114     2114           
=======================================
  Hits         4619     4619           
  Misses       1980     1980           
  Partials      181      181           

Flag	Coverage Δ
e2e	52.85% <ø> (-15.26%)	⬇️

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.