update Cargo.toml for release v2.5.9

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Version updated to 2.5.9
  • UI assets metadata updated

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

[coderabbitai]

Walkthrough

Version bump from 2.5.8 to 2.5.9 with corresponding updates to parseable_ui assets metadata. The assets URL version reference and SHA1 hash are updated to match the new release version.

Changes

Cohort / File(s)	Change Summary
Package Version & UI Assets Bump Cargo.toml	Version bumped: 2.5.8 → 2.5.9; assets-url path updated to reference v2.5.9 build; assets-sha1 hash updated to 881a1e93c8aff42d517953a7da98d8d03d623db2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update Cargo.toml for release v2.5.8 #1517: Bumps package version and updates parseable_ui assets-url and assets-sha1 for a successive release.
• chore: update Cargo.toml for release v2.5.7 #1515: Updates Cargo.toml version and parseable_ui asset metadata to a new release.
• chore: update Cargo.toml for release v2.5.6 #1511: Modifies package version and parseable_ui assets-url and assets-sha1 fields for release versioning.

Suggested reviewers

• nitisht

Poem

🐰 Hop! The version climbs with glee,
From 2.5.8 to .9, you see!
Assets and hashes, all aligned,
A clean release, perfectly defined! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is entirely missing, lacking all required sections including description, key changes, and testing/documentation checkboxes from the template.	Add a detailed description following the repository template, including the purpose of the release and verification that testing has been completed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating Cargo.toml for release v2.5.9, which matches the version bumps in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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