chore: update Cargo.toml for release v2.5.5

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Released version 2.5.5 with updated assets and dependencies.

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

[coderabbitai]

Walkthrough

Updates the Cargo.toml manifest to bump the package version from 2.5.4 to 2.5.5 and aligns the parseable_ui assets metadata with the corresponding version, including URL and SHA1 hash.

Changes

Cohort / File(s)	Summary
Version & Metadata Bump Cargo.toml	Incremented package version to 2.5.5; updated parseable_ui assets-url to reference v2.5.5/build.zip; updated assets-sha1 hash to match new build artifact

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update cargo toml for release 2.3.5 #1359 — Direct release bump pattern with identical Cargo.toml version and parseable_ui metadata updates.
• update Cargo toml for release v2.5.4 #1478 — Consecutive release update modifying the same metadata fields for a different version increment.
• chore: update Cargo.toml for release v2.4.2 #1416 — Matching manifest-only changes bumping package version and parseable_ui assets URL/SHA1.

Suggested reviewers

• nitisht

Poem

🐰 A tiny bump from four to five,
Cargo.toml comes alive,
Assets zip and hashes new,
Release dance—now versioned true! ✨

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided by the author, but the template requires a Description section with goals, solutions, and key changes.	Add a pull request description following the template, including: the goal (releasing v2.5.5), key changes (version bump from 2.5.4 to 2.5.5, asset URL and SHA1 updates), and completion of the required checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: update Cargo.toml for release v2.5.5' directly and clearly describes the main change, which is updating version metadata for a release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e91606f and 598ee23.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• Cargo.toml

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

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

🔇 Additional comments (2)

Cargo.toml (2)

3-3: LGTM! Version bump follows semantic versioning.

The patch version increment from 2.5.4 to 2.5.5 is correctly applied.

---

184-185: URL is accessible, but SHA1 hash requires manual verification.

The assets URL returns HTTP 200 and is reachable. However, verifying the SHA1 hash requires downloading the full file to confirm it matches 1ac252787c9d1f9ea41d588f96acf21af9734b1a. This should be validated either during the build process or through manual download before merge.

---

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