🔖 release: common@0.0.13, mobile@1.1.21, server@0.2.70

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

Patch Changes

• #820 cce29b9 Thanks @cruzdanilo! - 🥅 stabilize error fingerprints and titles

• #820 d1e6bec Thanks @cruzdanilo! - 🥅 distinguish contract reverts by route and reason

• Updated dependencies [4b635eb, 709cd32, 1902307, dffa26b]:

  • @exactly/server@0.2.70
  • @exactly/common@0.0.13

@exactly/common@0.0.13

Patch Changes

• #820 1902307 Thanks @cruzdanilo! - 🚚 extract revert reason for cross-package reuse

@exactly/server@0.2.70

Patch Changes

• #820 4b635eb Thanks @cruzdanilo! - 🥅 improve sentry grouping for external service failures

• #820 709cd32 Thanks @cruzdanilo! - 🥅 normalize contract reverts on sentry

• #770 dffa26b Thanks @nfmelendez! - ✨ add card statement

Summary by CodeRabbit

• Chores
  • Released version 1.1.21 with patch updates across packages.
  • Updated @exactly/server to 0.2.70 and @exactly/common to 0.0.13.
  • Stabilized error fingerprints and titles.
  • Enhanced contract revert differentiation by route and reason.
  • Cleaned up release metadata.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Deleted three changeset metadata files, added changelog entries for root/common/server, and bumped package versions/dependency workspace references across root, server, common, docs, and .maestro; no runtime code or public API changes.

Changes

Cohort / File(s)	Summary
Changeset Cleanup ​.changeset/mighty-readers-punch.md, ​.changeset/stale-owls-work.md, ​.changeset/tender-rules-worry.md, ​.changeset/famous-spiders-carry.md	Deleted four changeset metadata files — metadata-only removals, no code or API changes.
Server release server/package.json, server/CHANGELOG.md	Bumped server version to 0.2.70 and added 0.2.70 changelog entry (references to PRs/commits).
Root & workspace deps package.json, CHANGELOG.md	Bumped root package version to 1.1.21, updated workspace deps for @exactly/common -> ^0.0.13 and @exactly/server -> ^0.2.70, and added root changelog entry for 1.1.21.
Common package common/package.json, common/CHANGELOG.md	Bumped common to 0.0.13 and added corresponding changelog entry noting the cross-package revert-reason extraction.
Docs & tooling devDeps docs/package.json, .maestro/package.json	Updated devDependency workspace references to @exactly/common@^0.0.13 and @exactly/server@^0.2.70 (dev-only metadata changes).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• 🔖 release: mobile@1.1.19, server@0.2.69 #806: Related release cadence and bump of @exactly/server to 0.2.70 (same release lineage).
• 🔖 release: server@0.2.65 #779: Release metadata updates touching server changelog/package.json similar to this PR.
• 🔖 release: server@0.2.68 #793: Consecutive patch release for @exactly/server with related changelog and package bumps.

Suggested reviewers

• nfmelendez
• 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 clearly indicates a release for server@0.2.70, which directly matches the main objective of the PR—publishing a patch version bump and corresponding changelog/version updates.

_{✏️ 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 facilitates an automated patch release for the @exactly/server package, incrementing its version and incorporating a new feature. It's part of a standard release workflow managed by Changesets, ensuring that recent changes are published to npm.

Highlights

• Automated Release: This pull request was automatically generated by the Changesets release GitHub action to prepare for the release of @exactly/server@0.2.70.
• Version Bump: The @exactly/server package has been updated from 0.2.69 to 0.2.70.
• Feature Addition: A new card statement feature (✨ add card statement) has been included in this patch release.

Changelog

• .changeset/stale-owls-work.md
  • Removed the changeset file as its content has been incorporated into the release.
• server/CHANGELOG.md
  • Added a new entry for version 0.2.70 including the patch changes for adding a card statement.
• server/package.json
  • Updated the package version from 0.2.69 to 0.2.70.

Activity

• This pull request was automatically opened by the Changesets release GitHub action.
• The PR will be automatically updated if more changesets are added to the main branch before merging.

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]

Bug: The version of @exactly/server is bumped, but the corresponding dependency in the root package.json is not updated, creating an inconsistent workspace.
_{Severity: MEDIUM}

Suggested Fix

Update the devDependencies in the root package.json to reference the new version of the server package. The dependency for "@exactly/server" should be changed from "workspace:^0.2.69" to "workspace:^0.2.70". After this change, run pnpm install to update the pnpm-lock.yaml file accordingly and include it in the pull request.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: server/package.json#L3

Potential issue: The pull request updates the version of the `@exactly/server` package
to `0.2.70` but fails to update the corresponding dependency references in other
packages within the monorepo. Specifically, the root `package.json` still references
`"@exactly/server": "workspace:^0.2.69"`. While `pnpm` might correctly resolve the
version due to the caret range, this creates an inconsistent state in the repository.
This indicates an incomplete release process, as the `pnpm-lock.yaml` file is also not
updated, which can lead to unpredictable dependency resolution and potential build
failures in CI/CD or local development environments.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[gemini-code-assist]

Code Review

This pull request updates @exactly/server to version 0.2.70 as part of a standard release. A security audit confirmed no vulnerabilities of medium, high, or critical severity. The changes involve removing the changeset file, updating CHANGELOG.md to document the new card statement feature, and updating the version in package.json. The automated Changesets workflow seems correctly managed, and versioning is consistent. A minor observation was made regarding the engines field in package.json, which specifies ^24.13.0 for Node.js, likely a typo for ^20.13.0 or ^22.13.0.

[sentry]

✅ All tests passed.