Skip to content

chore(main): [bot] release t8s-cluster:9.7.0#2009

Merged
teutonet-bot merged 3 commits intomainfrom
release-please--branches--main--components--t8s-cluster
Mar 20, 2026
Merged

chore(main): [bot] release t8s-cluster:9.7.0#2009
teutonet-bot merged 3 commits intomainfrom
release-please--branches--main--components--t8s-cluster

Conversation

@teutonet-bot
Copy link
Copy Markdown
Contributor

@teutonet-bot teutonet-bot commented Mar 12, 2026

🤖 I have created a release beep boop

9.7.0 (2026-03-18)

Features

  • t8s-cluster/workload-cluster: extract storageClasses from TeutonetesCloud (#2004) (86570be)

Bug Fixes

  • t8s-cluster: use plain values for autoScaling (#2002) (5a28b1a)

This PR was generated with Release Please. See documentation.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the release of version 9.7.0 for the t8s-cluster Helm chart. It integrates a new feature that extracts storage classes from TeutonetesCloud and includes a bug fix addressing the use of plain values for auto-scaling configurations.

Highlights

  • New Feature: Extracted storageClasses from TeutonetesCloud for the t8s-cluster/workload-cluster component.
  • Bug Fix: Corrected the t8s-cluster configuration to use plain values for autoScaling.
  • Version Update: Released t8s-cluster Helm chart version 9.7.0.
Changelog
  • .github/release-please/manifest.json
    • Updated the t8s-cluster chart version to 9.7.0.
  • charts/t8s-cluster/CHANGELOG.md
    • Added new changelog entries for version 9.7.0.
    • Included a feature for extracting storageClasses from TeutonetesCloud.
    • Documented a bug fix for using plain values for autoScaling.
  • charts/t8s-cluster/Chart.yaml
    • Updated the chart version to 9.7.0.
Activity
  • This pull request was automatically generated by the teutonet-bot using Release Please.
  • The bot created a new release for t8s-cluster version 9.7.0.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 12, 2026

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This PR releases a new version (9.7.0) of the t8s-cluster Helm chart, updating version numbers in release configuration, chart metadata, and release notes.

Changes

Cohort / File(s) Summary
Release Configuration
.github/release-please/manifest.json
Bumped t8s-cluster version from 9.6.0 to 9.7.0.
Chart Metadata
charts/t8s-cluster/Chart.yaml
Updated chart version to 9.7.0 and updated sources URL reference to point to t8s-cluster-v9.7.0.
Release Notes
charts/t8s-cluster/CHANGELOG.md
Added changelog entry for version 9.7.0 documenting storage class extraction feature and autoScaling configuration fix.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested labels

autorelease: tagged

Suggested reviewers

  • tasches
  • cwrau
  • marvinWolff

Poem

🐰 A version bump hops into view,
9.7.0, fresh and new!
Storage classes shine, scaling's true,
Release-please manifests through and through! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the main purpose of the changeset: releasing version 9.7.0 of the t8s-cluster Helm chart, which is directly reflected in all modified files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--t8s-cluster
📝 Coding Plan
  • Generate coding plan for human review comments

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request automates the release of t8s-cluster:9.7.0. The changes primarily consist of version bumps and changelog updates. My review has identified two issues for improvement: an incorrect future date in the changelog and an outdated source URL in the Chart.yaml. I have left specific comments on these points, with one referencing a relevant repository rule. Addressing these will ensure the release metadata is accurate and consistent.

Comment thread charts/t8s-cluster/CHANGELOG.md Outdated
Comment thread charts/t8s-cluster/Chart.yaml
@teutonet-bot teutonet-bot force-pushed the release-please--branches--main--components--t8s-cluster branch 4 times, most recently from c27fb59 to d40d83a Compare March 17, 2026 09:44
@teutonet-bot teutonet-bot force-pushed the release-please--branches--main--components--t8s-cluster branch from 8d334ee to 11e4dd2 Compare March 18, 2026 09:56
@teutonet-bot teutonet-bot added this pull request to the merge queue Mar 20, 2026
Merged via the queue into main with commit b5d116d Mar 20, 2026
19 checks passed
@teutonet-bot teutonet-bot deleted the release-please--branches--main--components--t8s-cluster branch March 20, 2026 08:46
@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