Skip to content

chore(main): [bot] release base-cluster:9.3.2#1662

Merged
teutonet-bot merged 3 commits into
mainfrom
release-please--branches--main--components--base-cluster
Sep 2, 2025
Merged

chore(main): [bot] release base-cluster:9.3.2#1662
teutonet-bot merged 3 commits into
mainfrom
release-please--branches--main--components--base-cluster

Conversation

@teutonet-bot
Copy link
Copy Markdown
Contributor

@teutonet-bot teutonet-bot commented Sep 2, 2025

🤖 I have created a release beep boop

9.3.2 (2025-09-02)

Bug Fixes

  • base-cluster/monitoring: otherwise the metric will be duplicated if suspend is not set (#1661) (193c6b3)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Bug Fixes
    • Prevents duplicate monitoring metrics when “suspend” is not set in the base-cluster chart.
  • Documentation
    • Added changelog entry for version 9.3.2 with details of the metrics duplication fix.
  • Chores
    • Updated base-cluster chart to version 9.3.2 in release configuration.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Sep 2, 2025

Warning

Rate limit exceeded

@teutonet-bot has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 24 minutes and 28 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 183cf9c and 73ddf00.

📒 Files selected for processing (2)
  • charts/base-cluster/Chart.yaml (1 hunks)
  • charts/base-cluster/README.md (2 hunks)

Walkthrough

Bumps charts/base-cluster version from 9.3.1 to 9.3.2 in Chart.yaml and release manifest, and adds a CHANGELOG entry documenting a bug fix regarding duplicated metrics when suspend is not set. No functional code changes are included in this diff.

Changes

Cohort / File(s) Summary
Release manifest update
.github/release-please/manifest.json
Updated charts/base-cluster version reference from 9.3.1 to 9.3.2.
Chart metadata
charts/base-cluster/Chart.yaml
Bumped chart version field to 9.3.2; no other metadata changes.
Changelog documentation
charts/base-cluster/CHANGELOG.md
Added 9.3.2 entry noting bug fix for monitoring metric duplication when suspend is not set.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective Addressed Explanation
Fix monitoring metric duplication when suspend is not set (#1661) No implementation changes present; only version bump and changelog entry.

Assessment against linked issues: Out-of-scope changes

Code Change Explanation
Version bump in release manifest and Chart.yaml (.github/release-please/manifest.json, charts/base-cluster/Chart.yaml) These are release/metadata updates and do not implement the monitoring fix specified in #1661.
Changelog entry addition (charts/base-cluster/CHANGELOG.md) Documentation-only; does not modify monitoring logic required by #1661.

Possibly related PRs

Suggested labels

base-cluster

Suggested reviewers

  • cwrau
  • marvinWolff
  • tasches

Poem

I hop through charts, versions anew,
9.3.2—a tidy view.
No code to tweak, just notes to read,
A changelog carrot meets the need.
One small bump, then off I zoom—
Metrics tamed, in release bloom! 🥕✨

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-please--branches--main--components--base-cluster

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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
Copy Markdown

@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: 0

🧹 Nitpick comments (1)
charts/base-cluster/Chart.yaml (1)

19-20: Update sources tag to the new release tag

Keep metadata accurate by pointing the first sources entry to base-cluster-v9.3.2.

Apply this diff:

-  - https://github.com/teutonet/teutonet-helm-charts/tree/base-cluster-v9.3.1/charts/base-cluster
+  - https://github.com/teutonet/teutonet-helm-charts/tree/base-cluster-v9.3.2/charts/base-cluster
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 193c6b3 and 183cf9c.

📒 Files selected for processing (3)
  • .github/release-please/manifest.json (1 hunks)
  • charts/base-cluster/CHANGELOG.md (1 hunks)
  • charts/base-cluster/Chart.yaml (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-24T09:41:28.072Z
Learnt from: cwrau
PR: teutonet/teutonet-helm-charts#1604
File: charts/base-cluster/templates/monitoring/metrics-server/metrics-server.yaml:20-21
Timestamp: 2025-07-24T09:41:28.072Z
Learning: The official kubernetes-sigs/metrics-server Helm chart pins the image tag to a specific version in its values.yaml by default, ensuring reproducible deployments without requiring explicit tag specification in consuming charts.

Applied to files:

  • charts/base-cluster/Chart.yaml
🔇 Additional comments (3)
.github/release-please/manifest.json (1)

1-1: Version bump aligns with chart

charts/base-cluster set to 9.3.2; matches Chart.yaml change.

charts/base-cluster/CHANGELOG.md (1)

3-8: Changelog entry consistent with intent

Entry for 9.3.2 (2025-09-02) reflects the monitoring metric duplication fix and links to #1661 and the commit. No action needed.

charts/base-cluster/Chart.yaml (1)

22-22: Chart version bump looks good

Version updated to 9.3.2.

@teutonet-bot teutonet-bot added this pull request to the merge queue Sep 2, 2025
Merged via the queue into main with commit ffd8264 Sep 2, 2025
20 checks passed
@teutonet-bot teutonet-bot deleted the release-please--branches--main--components--base-cluster branch September 2, 2025 13:18
@teutonet-bot
Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants