Skip to content

chore: update release version in cargo toml #1333

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 3, 2025

Conversation

nikhilsinhaparseable
Copy link
Contributor

@nikhilsinhaparseable nikhilsinhaparseable commented Jun 3, 2025

Summary by CodeRabbit

  • Chores
    • Updated package version and related metadata to 2.3.2.

Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

Walkthrough

The package version in Cargo.toml was updated from 2.3.1 to 2.3.2, along with updates to the parseable_ui asset URLs and SHA-1 checksums to reflect the new release. No other dependencies or configurations were changed.

Changes

File(s) Change Summary
Cargo.toml Bumped package version to 2.3.2; updated parseable_ui asset URLs and SHA-1 checksum.

Possibly related PRs

Poem

A hop and a skip, a version anew,
2.3.2 shines with a checksum true!
URLs now point to the latest delight,
As Cargo.toml updates through the night.
With every release, the code hops ahead—
A rabbit’s joy in each version spread! 🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d4bf193 and 41fe0f9.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • Cargo.toml (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (10)
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu
  • GitHub Check: coverage
🔇 Additional comments (1)
Cargo.toml (1)

142-143:

✅ Verification successful

Validate parseable_ui asset metadata
Confirm that the assets-url and assets-sha1 entries match the actual published artifact for v2.3.2 to guarantee integrity.

Expected output: 35cfa3ab692ab0debf6666e5e2e1876fa7de4a02


🏁 Script executed:

#!/bin/bash
# Fetch the v2.3.2 build and compute its SHA-1 checksum
curl -sSL "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.3.2/build.zip" \
  | sha1sum | awk '{print $1}'

Length of output: 261


🏁 Script executed:

#!/bin/bash
# Fetch the v2.3.2 build and compute its SHA-1 checksum using Python
python3 - << 'EOF'
import hashlib, urllib.request, sys
url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.3.2/build.zip"
h = hashlib.sha1()
try:
    with urllib.request.urlopen(url) as r:
        for chunk in iter(lambda: r.read(8192), b""):
            h.update(chunk)
    print(h.hexdigest())
except Exception as e:
    print("ERROR:", e, file=sys.stderr)
    sys.exit(1)
EOF

Length of output: 146


🏁 Script executed:

#!/bin/bash
set -eo pipefail
# Fetch the v2.3.2 build with SSL verification disabled and compute its SHA-1 checksum
curl -sSk "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.3.2/build.zip" \
  | openssl dgst -sha1 | awk '{print $2}'

Length of output: 291


🏁 Script executed:

#!/bin/bash
# Fetch the v2.3.2 build over HTTPS without SSL verification and compute its SHA-1 checksum using Python
python3 - << 'EOF'
import ssl, hashlib, urllib.request, sys

url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.3.2/build.zip"
h = hashlib.sha1()
ctx = ssl._create_unverified_context()

try:
    with urllib.request.urlopen(url, context=ctx) as resp:
        for chunk in iter(lambda: resp.read(8192), b""):
            h.update(chunk)
    print(h.hexdigest())
except Exception as e:
    print("ERROR:", e, file=sys.stderr)
    sys.exit(1)
EOF

Length of output: 52


Verified parseable_ui asset metadata
The computed SHA-1 checksum for v2.3.2 matches the assets-sha1 entry in Cargo.toml (35cfa3ab692ab0debf6666e5e2e1876fa7de4a02). No changes needed.

@@ -1,6 +1,6 @@
[package]
name = "parseable"
version = "2.3.1"
version = "2.3.2"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Ensure version bump consistency
The crate version has been updated to 2.3.2. Please verify that this bump is reflected everywhere—CHANGELOG.md, documentation, CI/CD release scripts, and any other references to the old 2.3.1.


🏁 Script executed:

#!/bin/bash
# Verify no remaining references to the old version 2.3.1
rg -n '2\.3\.1'

Length of output: 313


Update remaining version references
We’ve bumped the crate to 2.3.2, but the old 2.3.1 still appears in several places. Please update all of these before merging:

• Cargo.lock (regenerate via cargo update or bump the lock entry)
• index.yaml

  • Line 36: appVersion: v2.3.1
  • Line 57: chart URL referencing parseable-2.3.1.tgz
  • Line 58: version: 2.3.1
    • helm/Chart.yaml
  • Line 5: version: 2.3.1
  • Line 6: appVersion: "v2.3.1"
    • helm/values.yaml
  • Line 4: tag: "v2.3.1"

After updating, verify CHANGELOG.md, documentation, and any CI/CD scripts also reflect 2.3.2.

🤖 Prompt for AI Agents
In Cargo.toml at line 3, the version has been updated to 2.3.2, but other files
still reference the old version 2.3.1. Update all occurrences of 2.3.1 to 2.3.2
in Cargo.lock (regenerate with cargo update), index.yaml (lines 36, 57, 58),
helm/Chart.yaml (lines 5 and 6), and helm/values.yaml (line 4). Also verify and
update CHANGELOG.md, documentation, and CI/CD scripts to consistently reflect
version 2.3.2 before merging.

@nitisht nitisht merged commit ad12b8d into parseablehq:main Jun 3, 2025
14 checks passed
@nikhilsinhaparseable nikhilsinhaparseable deleted the prepare-v2.3.2 branch June 3, 2025 10:53
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