Skip to content

update cargo.toml to prism v2.2.0 #1300

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
Apr 22, 2025

Conversation

nikhilsinhaparseable
Copy link
Contributor

@nikhilsinhaparseable nikhilsinhaparseable commented Apr 22, 2025

Summary by CodeRabbit

  • Chores
    • Updated the package version to 2.2.0.
    • Updated asset metadata to reflect the new version.

Copy link
Contributor

coderabbitai bot commented Apr 22, 2025

Walkthrough

The changes update the Cargo.toml file by incrementing the package version from 2.1.0 to 2.2.0. Additionally, the metadata for the parseable_ui package within the same file is modified to reference a new assets URL and an updated SHA1 checksum that correspond to the new version. No other dependencies, features, or configurations are changed, and there are no modifications to exported or public entities.

Changes

File(s) Change Summary
Cargo.toml Updated package version to 2.2.0; changed parseable_ui assets URL and SHA1.

Possibly related PRs

Suggested labels

for next release

Poem

A hop and a skip, a version anew,
Cargo.toml shines with a number true.
The UI assets now point to the sky,
With a fresh checksum waving hi!
Rabbits rejoice, for the build is bright—
2.2.0 brings us delight!
🐇✨


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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 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 3571f1c and ed67946.

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

3-3: Bump crate version to 2.2.0
The version field has been correctly updated to align with the new Prism release. Ensure that the crate is published under this version on crates.io and that any CI/CD workflows reflecting the version are adjusted if necessary.

Comment on lines +141 to +142
assets-url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.2.0/build.zip"
assets-sha1 = "6606fd794925eaa2c5e1815fd386c0682bea4f91"
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

Sync parseable_ui assets for v2.2.0
The assets-url and assets-sha1 metadata fields now point to the v2.2.0 build. Please verify that the SHA1 checksum matches the downloaded ZIP archive:

Also consider updating your CHANGELOG.md or release notes to document this version bump and metadata change.


🏁 Script executed:

#!/usr/bin/env bash
# Verify parseable_ui v2.2.0 assets checksum
curl -sSL "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.2.0/build.zip" -o build.zip
echo "6606fd794925eaa2c5e1815fd386c0682bea4f91  build.zip" | sha1sum --check

Length of output: 275


🏁 Script executed:

#!/usr/bin/env bash
# Verify parseable_ui v2.2.0 assets SHA1 using Python since sha1sum is unavailable
curl -sSL "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.2.0/build.zip" -o build.zip
EXPECTED="6606fd794925eaa2c5e1815fd386c0682bea4f91"
ACTUAL=$(python3 - << 'EOF'
import hashlib
print(hashlib.sha1(open('build.zip','rb').read()).hexdigest())
EOF
)
echo "Expected: $EXPECTED"
echo "Actual:   $ACTUAL"
if [ "$EXPECTED" != "$ACTUAL" ]; then
  echo "ERROR: SHA1 mismatch!"
  exit 1
fi
echo "OK: SHA1 matches."

Length of output: 577


SHA1 checksum verified for parseable_ui v2.2.0 assets
The assets-url and assets-sha1 entries in Cargo.toml now correctly reference v2.2.0 and the SHA1 matches the downloaded ZIP archive.

Please also update your documentation to reflect this release:

  • Add an entry in CHANGELOG.md (or your release notes) for v2.2.0, noting the asset URL and checksum update.

@nitisht nitisht merged commit 356ce8f into parseablehq:main Apr 22, 2025
14 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