🔖 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/server@0.2.44

Patch Changes

• #594 ddc66a8 Thanks @cruzdanilo! - ✨ integrate sardine

• #593 566a1f0 Thanks @cruzdanilo! - 🚑️ collect regardless of card status

---

Note

Release @exactly/server 0.2.44

• Update CHANGELOG.md with patch entries: integrate sardine and collect regardless of card status
• Bump package.json version from 0.2.43 to 0.2.44
• Remove applied changesets in .changeset/

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

Summary by CodeRabbit

• New Features

  • Added Sardine integration.

• Bug Fixes

  • Fixed data collection to work regardless of card status.

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

[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 generated by the Changesets GitHub action. Its primary purpose is to publish a new patch version, 0.2.44, of the @exactly/server package to npm. This new version incorporates a critical fix to ensure data collection proceeds irrespective of the card's current status, thereby improving the robustness of the server's data handling.

Highlights

• New Release Version: The @exactly/server package has been bumped to version 0.2.44.
• Patch Fix Included: This release includes a patch fix that ensures data collection occurs regardless of the card's status.
• Automated Changelog Update: The CHANGELOG.md for the server package has been automatically updated to reflect the new version and its associated changes.

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, automatically generated by the Changesets release action, prepares a new patch release for the @exactly/server package, version 0.2.44. The changes consist of updating the version in package.json, adding the corresponding entry to CHANGELOG.md, and removing the source changeset file. These modifications are standard for an automated release workflow and appear correct. As there are no changes to application logic in this pull request, I have no specific comments.

[coderabbitai]

Walkthrough

These changes represent a version release workflow where pending changesets are being consumed into the changelog, the package version is being bumped from 0.2.43 to 0.2.44, and corresponding changeset files are being removed.

Changes

Cohort / File(s)	Summary
Changeset Consumption .changeset/forty-ads-lie.md, .changeset/rotten-terms-move.md	Deleted and modified changeset files after their changes were integrated into the changelog. Entries described "integrate sardine" and "collect regardless of card status" features.
Version Release server/package.json, server/CHANGELOG.md	Version bumped to 0.2.44 with two new patch entries added to changelog crediting PRs #594 and #593 by @cruzdanilo.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• nfmelendez

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title '🔖 new release' accurately reflects the PR's purpose—automating a patch release (v0.2.44) via Changesets, with version bumps and changelog updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ddc66a8 and 5e774f8.

📒 Files selected for processing (4)

• .changeset/forty-ads-lie.md
• .changeset/rotten-terms-move.md
• server/CHANGELOG.md
• server/package.json

💤 Files with no reviewable changes (2)

• .changeset/rotten-terms-move.md
• .changeset/forty-ads-lie.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'

Files:

• server/CHANGELOG.md

**/*.{mdc,md}

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

**/*.{mdc,md}: All narrative text in internal documentation (.mdc files, README.md) must be lowercase with no exceptions
When referring to code concepts in prose, use regular lowercase words and put the correctly-cased identifier inside backticks
Code examples inside backticks or code fences must strictly follow the casing rules defined in the style guide

Files:

• server/CHANGELOG.md

🧠 Learnings (1)

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

Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/dev.mdc:0-0
Timestamp: 2025-12-23T19:56:56.392Z
Learning: Server (exactly/server) uses Hono (framework), Node.js, Drizzle ORM (database), and PostgreSQL

Applied to files:

• server/package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

🔇 Additional comments (2)

server/package.json (1)

3-3: Version bump is appropriate for the patch release.

The increment from 0.2.43 to 0.2.44 correctly reflects the two patch changes described in the PR objectives (PRs #594 and #593). No dependency modifications detected, which is appropriate for a patch release.

server/CHANGELOG.md (1)

3-9: CHANGELOG entry is structurally correct and content is accurate.

The new 0.2.44 section properly documents:

• Sequential heading levels (## for version, ### for section type)
• Correct reference to PRs #594 and #593 with commit hashes and author attribution
• Patch change descriptions matching PR objectives
• Proper blank-line spacing around block elements
• The existing 0.2.43 entry preserved below without modification

The release automation workflow is working as expected.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Lines exceed the 120-character markdown limit.

Lines 7 and 9 exceed the 120-character-per-line guideline (both are ~175+ characters). While this CHANGELOG content is auto-generated by the Changesets release action (per PR summary), the coding guidelines specify the limit applies to all markdown files.

Recommendation: Consider adding a carve-out in the coding guidelines for files auto-generated by well-known release tooling (Changesets), as manual reformatting would conflict with the automated workflow.

🤖 Prompt for AI Agents

In server/CHANGELOG.md around lines 3 to 9, two changelog entries exceed the
120-character-per-line markdown limit; either wrap those long lines to <=120
characters (reflow the two PR/commit lines) or, preferable, add an explicit
exception for auto-generated Changesets output by updating the repository’s
markdown linting/coding-guideline configuration to ignore CHANGELOG.md (or the
Changesets output path) and update the documentation to state the carve-out;
apply one of these fixes and commit with a short message explaining the chosen
approach.