Skip to content

Conversation

@nikhilsinhaparseable
Copy link
Contributor

@nikhilsinhaparseable nikhilsinhaparseable commented Jan 10, 2026

Summary by CodeRabbit

  • Chores
    • Patch release: bumped version to 2.5.8
    • Updated UI component assets to align with new version

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 10, 2026

Walkthrough

Cargo.toml manifest file updated to bump package version from 2.5.7 to 2.5.8 and refresh published UI asset references (assets-url and assets-sha1) to correspond with the new version.

Changes

Cohort / File(s) Summary
Package Version & Asset Metadata
Cargo.toml
Bumped package version to 2.5.8; updated package.metadata.parseable_ui assets-url and assets-sha1 from v2.5.7 to v2.5.8

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • nitisht

Poem

🐰 A version hops from seven to eight,
With assets polished, fresh and great!
The manifest gleams, the checksums align,
Another release shines with delight divine! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning No pull request description was provided, while the repository template requires sections for issue fixes, description, and testing/documentation checklists. Add a pull request description following the template, including the description section and applicable pre-merge checklists.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: updating Cargo.toml version from 2.5.7 to 2.5.8 for release v2.5.8.
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.


📜 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 18c1a77 and 3b3159d.

⛔ 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 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 Default x86_64-unknown-linux-gnu
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: coverage
  • GitHub Check: Build Kafka aarch64-apple-darwin
🔇 Additional comments (2)
Cargo.toml (2)

3-3: LGTM - Version bump is consistent with release objectives.

The package version has been correctly bumped from 2.5.7 to 2.5.8 for this release.


184-185: Verify the asset URL is accessible and SHA1 hash is correct.

The UI assets have been updated to reference v2.5.8. The asset URL (https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.5.8/build.zip) is accessible and responds with HTTP 200. However, verify that:

  1. The SHA1 hash d8f31e20f1f5761891060e42b619ff6505a2dbba matches the actual content at the URL
  2. The build corresponds to the correct version (v2.5.8, which is present in the URL path)

To verify the SHA1 hash, download the asset and compare its hash against the expected value using sha1sum or shasum -a 1.


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

@nikhilsinhaparseable nikhilsinhaparseable merged commit f73fd87 into parseablehq:main Jan 10, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants