Update nuqs package version to 2.5.0

[adamghaida]

READ CAREFULLY THEN REMOVE

Remove bullet points that are not relevant.

PLEASE REFRAIN FROM USING AI TO WRITE YOUR CODE AND PR DESCRIPTION. IF YOU DO USE AI TO WRITE YOUR CODE PLEASE PROVIDE A DESCRIPTION AND REVIEW IT CAREFULLY. MAKE SURE YOU UNDERSTAND THE CODE YOU ARE SUBMITTING USING AI.

• Pull requests that do not follow these guidelines will be closed without review or comment.
• If you use AI to write your PR description your pr will be close without review or comment.
• If you are unsure about anything, feel free to ask for clarification.

Description

Please provide a clear description of your changes.

---

Type of Change

Please delete options that are not relevant.

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature with breaking changes)
• 📝 Documentation update
• 🎨 UI/UX improvement
• 🔒 Security enhancement
• ⚡ Performance improvement

Areas Affected

Please check all that apply:

• Email Integration (Gmail, IMAP, etc.)
• User Interface/Experience
• Authentication/Authorization
• Data Storage/Management
• API Endpoints
• Documentation
• Testing Infrastructure
• Development Workflow
• Deployment/Infrastructure

Testing Done

Describe the tests you've done:

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• Cross-browser testing (if UI changes)
• Mobile responsiveness verified (if UI changes)

Security Considerations

For changes involving data or authentication:

• No sensitive data is exposed
• Authentication checks are in place
• Input validation is implemented
• Rate limiting is considered (if applicable)

Checklist

• I have read the CONTRIBUTING document
• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in complex areas
• I have updated the documentation
• My changes generate no new warnings
• I have added tests that prove my fix/feature works
• All tests pass locally
• Any dependent changes are merged and published

Additional Notes

Add any other context about the pull request here.

Screenshots/Recordings

Add screenshots or recordings here if applicable.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.

---

Summary by cubic

Upgrade nuqs to 2.5.0 to pick up latest fixes and compatibility updates. No app code changes; only dependency and lockfile updates.

• Dependencies
  • Bumped nuqs from 2.4.0 to 2.5.0 in apps/mail.
  • Lockfile: replaces mitt with @standard-schema/spec.
  • Adds optional peer @tanstack/react-router; React 19 and React Router support unchanged.

Summary by CodeRabbit

• Chores
  • Updated a third-party library (nuqs) to version 2.5.0 to align with upstream improvements and maintain compatibility.
  • Expect minor behind-the-scenes performance and stability enhancements; no user-facing features or interface changes.
  • Existing behavior should remain unchanged. Please report any unexpected issues after the update.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Updated nuqs dependency version in apps/mail/package.json from 2.4.0 to 2.5.0. No other files or declarations changed.

Changes

Cohort / File(s)	Summary
Dependency bump apps/mail/package.json	Bumped nuqs from 2.4.0 → 2.5.0 in dependencies; no other edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

content

Poem

Version sails set, tiny thrust applied,
nuqs to 2.5—engines slightly amplified.
One file tweaked, like a micro-burn in space,
Course corrected, clean and to the base.
Minimal delta, maximum glide—
Onward we iterate, enjoy the ride. 🚀

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 08-22-updating_nuqs

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[cubic-dev-ai]

No issues found across 2 files

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e67c76a and bd7318c.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• apps/mail/package.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/package.json

📄 CodeRabbit inference engine (AGENT.md)

Workspace packages use catalog versioning for shared dependencies

Files:

• apps/mail/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: cubic · AI code reviewer

🔇 Additional comments (1)

apps/mail/package.json (1)

88-88: All nuqs imports and API usages are consistent with v2.5.0 – ready for liftoff.

I verified that:

• There is exactly one declaration of "nuqs": "2.5.0" in apps/mail/package.json, with no other versions or catalog: prefixes anywhere else.
• All imports come directly from 'nuqs' or the official adapter path 'nuqs/adapters/react-router/v7', and no legacy sub-paths (router, next, etc.) are used.
• Every useQueryState, parseAs*, and other common API call matches the v2.5.x signatures (key-only calls, defaultValue/options objects, parser chaining) with no deprecated patterns.

Everything aligns with the 2.5.x API surface, so we’re clear to merge.