Skip to content

update Cargo.toml for release v2.9.0#1677

Merged
nikhilsinhaparseable merged 1 commit into
parseablehq:mainfrom
nikhilsinhaparseable:prepare-v2.9.0
Jun 13, 2026
Merged

update Cargo.toml for release v2.9.0#1677
nikhilsinhaparseable merged 1 commit into
parseablehq:mainfrom
nikhilsinhaparseable:prepare-v2.9.0

Conversation

@nikhilsinhaparseable

@nikhilsinhaparseable nikhilsinhaparseable commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Version bump to 2.9.0 with updated build assets.

@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 87f500bc-f945-4710-8666-20ec5e906d4e

📥 Commits

Reviewing files that changed from the base of the PR and between f4fd9df and df87448.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • Cargo.toml

Walkthrough

This PR increments the Parseable crate version from 2.8.0 to 2.9.0 in Cargo.toml and updates the package metadata to point the UI assets distribution URL and integrity checksum to the corresponding v2.9.0 build artifact.

Changes

Version 2.9.0 Release

Layer / File(s) Summary
Package version and UI assets metadata bump
Cargo.toml
Crate version is bumped to 2.9.0, and the parseable_ui assets URL and checksum are updated to reference the v2.9.0 build zip artifact from the S3 bucket.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • parseablehq/parseable#1656: Both PRs only update Cargo.toml's version and package.metadata.parseable_ui (assets-url and assets-sha1) for a specific release (v2.8.0 vs v2.9.0), making them directly related.
  • parseablehq/parseable#1407: Both PRs adjust Cargo.toml release metadata by bumping the package version and updating package.metadata.parseable_ui.assets-url/assets-sha1 to match the corresponding build artifact version.
  • parseablehq/parseable#1596: Both PRs modify Cargo.toml's [package] version and the package.metadata.parseable_ui assets-url/assets-sha1 to point to the corresponding release build zip for the new version.

Suggested reviewers

  • nitisht
  • parmesant

Poem

🐰 A version bump, so small and neat,
From 2.8 to 2.9 complete!
The assets align with checksums tight,
Release metadata shines just right! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request has no description provided, but the repository requires a structured description following a template with sections like Description and a checklist of verification items. Add a pull request description following the template, including the rationale for the version update and completion of the pre-merge checklist items.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title directly and clearly describes the main change: updating Cargo.toml specifically for release v2.9.0, which matches the version bump and metadata updates in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@nikhilsinhaparseable nikhilsinhaparseable merged commit cc0dd62 into parseablehq:main Jun 13, 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.

3 participants