🔖 release: mobile@1.1.14, server@0.2.64

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

Patch Changes

• #774 e2620dc Thanks @cruzdanilo! - 🥅 fingerprint passkey errors by message, drop expected ones

• Updated dependencies [de02358, 48a97e6]:

  • @exactly/server@0.2.64

@exactly/server@0.2.64

Patch Changes

• #772 de02358 Thanks @cruzdanilo! - 🥅 handle no-proposal as success in proposal execution

• #771 48a97e6 Thanks @cruzdanilo! - 🧵 guarantee nonce order in proposal execution

[coderabbitai]

Walkthrough

This is a version release commit that consolidates pending changesets. Two changeset files are removed, the server package version is bumped from 0.2.63 to 0.2.64, and the CHANGELOG is updated with two bug fixes related to proposal execution handling.

Changes

Cohort / File(s)	Summary
Changeset Cleanup .changeset/brave-falcon-catch.md, .changeset/bright-foxes-race.md	Removed changeset files documenting patch version bump and two proposal execution fixes.
Version Release server/package.json, server/CHANGELOG.md	Bumped version from 0.2.63 to 0.2.64 and added corresponding changelog entries documenting fixes for proposal execution (no-proposal handling and nonce ordering).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• PRs #768, #595, #697, #734: Similar release metadata updates for @exactly/server version bumps and changeset consolidation.

Suggested reviewers

• nfmelendez

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main purpose of the changeset: releasing version 0.2.64 of the server package with specific patch fixes.

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

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 automates the release of the @exactly/server package, bumping its version to 0.2.64. The update incorporates a specific change that improves the handling of proposal execution by treating the absence of a proposal as a successful state.

Highlights

• Server Version Update: The @exactly/server package has been updated to version 0.2.64.
• Proposal Execution Logic: The server now correctly handles scenarios where no proposal exists as a successful outcome during proposal execution.

Changelog

• .changeset/brave-falcon-catch.md
  • Removed the temporary changeset file after its content was incorporated into the release.
• server/CHANGELOG.md
  • Added a new entry for version 0.2.64, detailing the patch change for handling 'no-proposal' as success in proposal execution.
• server/package.json
  • Updated the version field from 0.2.63 to 0.2.64.

Activity

• This pull request was automatically opened by the Changesets release GitHub action to facilitate the 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. ↩

[devin-ai-integration]

✅ Devin Review: No Issues Found

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

[sentry]

✅ All tests passed.

[gemini-code-assist]

Code Review

This pull request is an automated release for version 0.2.64 of the @exactly/server package. The changes consist of updating the package version, adding a new entry to the changelog, and removing the corresponding changeset file. These changes are standard for a release and appear to be correct. The underlying code change, which handles NoProposal as a success case during proposal execution, is a good reliability improvement. I have no specific comments as the changes in this PR are all related to the automated release process.