chore: update Cargo.toml for release v2.5.6

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Updated package version to 2.5.6 with refreshed asset references.

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

[coderabbitai]

Walkthrough

This pull request bumps the package version from 2.5.5 to 2.5.6 and updates the corresponding parseable_ui asset references, including the assets URL and SHA1 checksum, to align with the new version.

Changes

Cohort / File(s)	Summary
Version & Asset Updates Cargo.toml	Bumped package version from 2.5.5 to 2.5.6; updated [package.metadata.parseable_ui] assets-url and assets-sha1 to reference v2.5.6 assets

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update Cargo.toml for release v2.5.5 #1506: Both PRs update the same Cargo.toml fields (package version and parseable_ui assets-url/assets-sha1) for successive releases (v2.5.4→2.5.5 and v2.5.5→2.5.6).
• update Cargo toml for release v2.5.4 #1478: Both PRs modify Cargo.toml's package version and the [package.metadata.parseable_ui] assets-url/assets-sha1 entries.
• release 2.5.0 updates #1461: Both PRs modify the same Cargo.toml metadata for package.metadata.parseable_ui with asset reference updates.

Suggested reviewers

• nitisht

Poem

🐰 A version so fine, now two-five-six shines,
Assets aligned with their new checksummed lines,
Cargo bumps up, the manifest agrees,
The release is ready to go with such ease!

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided. The required template includes Description, testing checklist, and documentation requirements, all of which are missing.	Add a description following the template: include what was changed (version bump details), confirm testing was done, and indicate if any documentation updates were needed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: update Cargo.toml for release v2.5.6' clearly and accurately describes the main change: a version bump for release preparation.
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 bfb9e06 and facb5f7.

⛔ 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: Build Kafka x86_64-unknown-linux-gnu
• GitHub Check: Build Default aarch64-apple-darwin
• GitHub Check: Build Default x86_64-unknown-linux-gnu
• GitHub Check: Build Default x86_64-pc-windows-msvc
• GitHub Check: Build Kafka aarch64-apple-darwin
• GitHub Check: Build Default aarch64-unknown-linux-gnu
• GitHub Check: coverage
• GitHub Check: Quest Smoke and Load Tests for Standalone deployments
• GitHub Check: Quest Smoke and Load Tests for Distributed deployments

🔇 Additional comments (2)

Cargo.toml (2)

3-3: LGTM: Version bump is correct.

The patch version increment from 2.5.5 to 2.5.6 is appropriate and aligns with the PR objectives.

---

184-185: The assets URL is accessible and the SHA1 checksum verification is already built into the build process.

The URL https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.5.6/build.zip is confirmed accessible and returns HTTP 200. The SHA1 checksum will be automatically validated during the build by build.rs, which downloads the file, computes its SHA1 using Sha1::from(), and asserts it matches the value specified in Cargo.toml. If the checksum doesn't match, the build will fail at this assertion point, preventing any broken builds from proceeding.

---

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