update Cargo toml for release v2.4.3

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Updated asset metadata to reference the latest packaged UI resources, ensuring the app bundles the most up-to-date assets.
  • Improves consistency across environments and aligns asset versions used during build and deployment.
  • No user-facing functionality or behavior changes; performance and features remain the same.
  • No action required from users.

[coderabbitai]

Walkthrough

Updated the assets-sha1 value in Cargo.toml under [package.metadata.parseable_ui] to a new checksum in both occurrences. No logic, code, or API changes.

Changes

Cohort / File(s)	Summary
Metadata checksum update Cargo.toml	Updated [package.metadata.parseable_ui].assets-sha1 from 1b7db84c0365f48870745989be0640ecfe8f06fd to abc3842eef4ad66375299bc6f71d5cd5b01c698b (in both occurrences).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update Cargo.toml for release v2.4.3 #1436 — Updates the same Cargo.toml assets-sha1 field; this PR supersedes that checksum.
• chore: update cargo toml for release v2.4.1 #1407 — Modifies [package.metadata.parseable_ui].assets-sha1 in Cargo.toml, same field and file.
• update parseable version, assets url and sha #1315 — Changes the parseable_ui assets-sha1 checksum in Cargo.toml, directly related.

Suggested reviewers

• nitisht

Poem

A nibble of hashes, a checksum delight,
I hop through Cargo on a moonlit night.
Old sum burrowed, new one in sight—
Thump goes the paw, metadata right.
Carrots secured, the build’s airtight. 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	No pull request description was provided; the repository's required template requests a "Fixes #XXXX" line, a "Description" section describing goal, rationale, and key changes, and a testing/documentation checklist, none of which are present, so the description is incomplete. Because these required sections are missing the check fails.	Please populate the PR description using the repository template: add a Fixes line if applicable, include a concise Description explaining the goal and rationale (e.g., that the assets SHA-1 checksum in Cargo.toml was updated for v2.4.3), list key changes, and complete the testing/documentation checklist or mark items as not applicable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "update Cargo toml for release v2.4.3" accurately summarizes the primary change in the changeset (updates to Cargo.toml for the v2.4.3 release), is concise and focused, and aligns with the raw_summary which shows only checksum updates in Cargo.toml. It is clear enough for a teammate scanning history to understand the main intent. Minor stylistic nit: capitalize "Cargo.toml" for readability.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

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

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Cargo.toml (1)

162-165: Non-blocking: consider moving to SHA‑256 for asset integrity.

SHA‑1 is collision-prone. When feasible, migrate the pipeline (Cargo.toml key, build.rs verification, release docs) to SHA‑256.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b5d85ef and 944252d.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

Cargo.toml (2)

162-165: Incorrect — only one [package.metadata.parseable_ui] block found

Repo search shows a single instance in Cargo.toml (lines 162–165) containing assets-sha1; no other occurrences detected.

Likely an incorrect or invalid review comment.

---

164-164: Verify hosted artifact SHA‑1 matches Cargo.toml

Sandbox verification failed: openssl not found. Confirm the SHA‑1 of build.zip at https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.4.3/build.zip equals abc3842eef4ad66375299bc6f71d5cd5b01c698b (Cargo.toml, line 164). Suggested command (macOS/Linux): curl -fsSL "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.4.3/build.zip" -o build.zip && shasum -a 1 build.zip (or sha1sum build.zip).