chore: update to helm release v2.3.2

[nitisht]

Also update comments in the release action

Summary by CodeRabbit

• Chores
  • Updated workflow name and documentation for release builds to clarify Docker support.
  • Renamed a job in the release workflow for improved clarity.
  • Updated Helm chart and application version to 2.3.2.
  • Updated Docker image tag to v2.3.2 in deployment configuration.
  • Added a new Helm chart entry for version 2.3.2 and refreshed timestamps for all chart versions.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update revises the release workflow to clarify Docker build steps and renames a related job. The Helm chart and Docker image tags are incremented from version 2.3.1 to 2.3.2. The Helm chart index is updated with a new entry for version 2.3.2 and refreshed timestamps.

Changes

Files / Areas	Change Summary
.github/workflows/release.yml	Added workflow description, renamed job from push-docker-image to build-push-docker-image.
helm/Chart.yaml, helm/values.yaml	Updated Helm chart version and Docker image tag from 2.3.1 to 2.3.2.
index.yaml	Added Helm chart entry for 2.3.2, updated created and generated timestamps for all chart versions.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant Docker Hub
    participant GitHub Releases

    Developer->>GitHub Actions: Push tag v2.3.2
    GitHub Actions->>GitHub Actions: Build Parseable (Linux, Mac, Windows, Docker)
    GitHub Actions->>GitHub Releases: Publish artifacts & checksums
    GitHub Actions->>Docker Hub: Push Docker image (tagged v2.3.2)

Loading

Possibly related PRs

• parseablehq/parseable#1336: Renames the Docker image job and adds workflow comments, directly related to the workflow changes in this PR.
• parseablehq/parseable#1319: Updates Helm chart version, image tag, and index.yaml metadata, similar to the version bump and metadata updates in this PR.
• parseablehq/parseable#1328: Updates Helm chart and index.yaml for version 2.3.1, preceding and directly related to the 2.3.2 updates in this PR.

Poem

A hop and a skip, the version ascends,
From 2.3.1 to .2, the release never ends.
Helm charts refreshed, Docker tags anew,
Workflows renamed for a clearer view.
🐇 With every commit, the garden grows bright—
Shipping new features, from morning till night!

---

📜 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 2cd3381 and 74628cb.

📒 Files selected for processing (4)

• .github/workflows/release.yml (2 hunks)
• helm/Chart.yaml (1 hunks)
• helm/values.yaml (1 hunks)
• index.yaml (63 hunks)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[nitisht]

Skipping tests because this doesn't involve code change.