chore: update cargo toml for release v2.4.1

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Bumped application version to 2.4.1 for release.
  • Updated UI asset references to the v2.4.1 build, including new download URL and checksum for integrity verification.
  • Applied the same updates across all relevant configuration blocks to keep references consistent.
  • No user-facing feature changes; this aligns packaged assets with the new version for this release cycle.

[coderabbitai]

Walkthrough

Bumped package version to 2.4.1 in Cargo.toml and updated parseable_ui asset URL and SHA-1 checksum in both metadata blocks to point to v2.4.1 assets.

Changes

Cohort / File(s)	Summary of changes
Release version and UI asset metadata Cargo.toml	Updated [package] version 2.4.0→2.4.1. In both [package.metadata.parseable_ui] blocks, changed assets-url to v2.4.1 build.zip and assets-sha1 to 19eec4d38b978270eca1026325350e38c235ac31.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update cargo toml for release v2.4.0 #1385 — Prior release bump updating the same Cargo.toml fields (2.3.5→2.4.0).
• chore: update cargo toml for release 2.3.5 #1359 — Similar change set updating version and parseable_ui asset URL/SHA1.
• prepare for release v2.1.1 #1296 — Updates the same Cargo.toml metadata fields for a previous release.

Poem

A nibble of numbers, hop to .1,
I thump my paw—another build begun!
New zip on the wire, new hash in the sun,
Version carrots stacked, neatly one by one.
Squeak! goes the tag—2.4.1.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

Cargo.toml (1)

160-161: Consider migrating asset integrity to SHA-256 (future-proofing)

SHA-1 is collision-prone. If feasible in a future release, consider switching to SHA-256 (and updating build.rs or wherever this is validated). The repo already depends on sha2, so adding sha2 as a build-dependency could simplify the change.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
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 ed19109 and bd6f262.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml (2 hunks)

⏰ 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). (10)

• GitHub Check: Build Default aarch64-apple-darwin
• GitHub Check: Build Default x86_64-pc-windows-msvc
• GitHub Check: Build Default aarch64-unknown-linux-gnu
• GitHub Check: Build Kafka x86_64-unknown-linux-gnu
• GitHub Check: Build Kafka aarch64-apple-darwin
• GitHub Check: Build Default x86_64-apple-darwin
• GitHub Check: Build Default x86_64-unknown-linux-gnu
• GitHub Check: Quest Smoke and Load Tests for Standalone deployments
• GitHub Check: Quest Smoke and Load Tests for Distributed deployments
• GitHub Check: coverage

🔇 Additional comments (1)

Cargo.toml (1)

160-161: Manual Verification: UI Asset URL and Checksum

• Confirm the URL in Cargo.toml (line 160) is reachable and returns HTTP 200.
• Download the asset and compute its SHA-1 checksum; ensure it matches the value on line 161 (19eec4d38b978270eca1026325350e38c235ac31).
• Verify there are no other [package.metadata.parseable_ui] blocks pointing to older versions elsewhere in the repository.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Version bump to 2.4.1 — LGTM

Looks consistent with the PR objective. No functional concerns on this line.

If this is a workspace or there are other manifests, quickly verify no stale 2.4.0 references remain:

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail
# Find any lingering references to v2.4.0 in manifests or docs
rg -n --hidden -S 'v2\.4\.0|version\s*=\s*"2\.4\.0"'

Length of output: 187

---

Stale 2.4.0 references found – please update to 2.4.1

The version bump in Cargo.toml is correct, but there are still outdated references in other manifests:

• index.yaml (line 36):
  change appVersion: v2.4.0 → appVersion: v2.4.1
• helm/Chart.yaml (line 6):
  change appVersion: "v2.4.0" → appVersion: "v2.4.1"
• helm/values.yaml (line 4):
  change tag: "v2.4.0" → tag: "v2.4.1"

Suggested diff:

 index.yaml | 1 line
-    appVersion: v2.4.0
+    appVersion: v2.4.1

 helm/Chart.yaml | 1 line
-appVersion: "v2.4.0"
+appVersion: "v2.4.1"

 helm/values.yaml | 1 line
-    tag: "v2.4.0"
+    tag: "v2.4.1"

Once these are updated, the version bump will be fully consistent across the repo.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In Cargo.toml around line 3, version has been bumped to 2.4.1 but other
manifests still reference 2.4.0; update index.yaml (line 36) changing
appVersion: v2.4.0 → appVersion: v2.4.1, update helm/Chart.yaml (line 6)
changing appVersion: "v2.4.0" → appVersion: "v2.4.1", and update
helm/values.yaml (line 4) changing tag: "v2.4.0" → tag: "v2.4.1" so all version
references are consistent.