Skip to content

Conversation

@bradynwalsh
Copy link
Contributor

@bradynwalsh bradynwalsh commented Mar 22, 2025

Description

Updates Helm chart release to v1.7.5


Summary by CodeRabbit

  • New Features
    • Enhanced chart metadata now includes updated dependencies and standardized creation timestamps for improved consistency.
  • Chores
    • Upgraded the chart and application version to 1.7.5.
    • Updated the container image tag to 1.7.5 for seamless deployment.

These updates ensure that users receive the latest version improvements along with refined metadata for a smoother deployment experience.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 22, 2025

Walkthrough

The changes update the Parseable Helm chart versioning and metadata. Both helm/Chart.yaml and helm/values.yaml now reference version 1.7.5 instead of 1.7.3. Additionally, index.yaml incorporates a new entry for the parseable chart with detailed metadata, including dependencies, maintainers, and updated created timestamps.

Changes

Affected File(s) Change Summary
helm/Chart.yaml, helm/values.yaml Updated version numbers and image tag from 1.7.3 to 1.7.5.
index.yaml Added a new parseable chart entry with comprehensive metadata and updated created timestamps.

Poem

I’m a bunny hopping in the code,
Skipping through updates on my humble road.
Versions bloom like carrots in spring,
A cheerful leap for every change they bring.
1.7.5 shines bright—oh what a joyful hop! 🐰🌟


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8ac3105 and e7bcdd6.

📒 Files selected for processing (3)
  • helm/Chart.yaml (1 hunks)
  • helm/values.yaml (1 hunks)
  • index.yaml (58 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (10)
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments
  • GitHub Check: coverage
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
🔇 Additional comments (4)
helm/values.yaml (1)

1-5: Updated Image Tag Version
The update from "v1.7.3" to "v1.7.5" on line 4 is correctly applied for the Parseable image. Please verify that the Docker image tagged as "v1.7.5" exists and is compatible with the changes in the chart.

helm/Chart.yaml (1)

1-7: Synchronize Chart Versioning
The version and appVersion fields (lines 5–6) have been updated to reflect the new release version 1.7.5. This change is consistent with the values in helm/values.yaml. Double-check that any release automation or CI pipelines that reference these fields are updated accordingly.

index.yaml (2)

35-58: Insertion of New Chart Entry for v1.7.5
A new entry for the Parseable chart (lines 35–58) is added with version 1.7.5. The metadata—including appVersion, the updated timestamp (created), dependency listings, digest, and URLs—appears to follow the correct structure. Please confirm that the digest value is correct and corresponds to the chart package built for version 1.7.5, and that the dependency information (for vector and fluent-bit) matches your intended versions.


59-63: Updated Timestamp for Existing Chart Entry (v1.7.3)
The existing Parseable chart entry for version 1.7.3 (beginning at line 59 with an updated created timestamp on line 61) now uses the new timestamp format. Ensure that this update is intentional—for example, if it is part of a regeneration of the index file—and that the historical data for older versions remains correct for version tracking and rollback scenarios.


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.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 22, 2025

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@bradynwalsh
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@bradynwalsh
Copy link
Contributor Author

recheck

nitisht added a commit to parseablehq/.github that referenced this pull request Mar 22, 2025
@nitisht
Copy link
Member

nitisht commented Mar 22, 2025

Thanks you for the PR @bradynwalsh much appreciated.

@nitisht nitisht merged commit bd3bc8b into parseablehq:main Mar 22, 2025
14 of 15 checks passed
@bradynwalsh bradynwalsh deleted the helm-v1.7.5 branch March 23, 2025 00:55
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