fix(base-cluster/docs): there is no 9.0.0 release for now...

[cwrau]

Summary by CodeRabbit

• Documentation
  • Updated the migration section formatting in the README to use a horizontal rule instead of a heading for the 8.x.x to 9.0.0 upgrade. No content changes were made.

[coderabbitai]

Walkthrough

The changes update the migration section formatting in both the charts/base-cluster/README.md and its template, replacing the markdown heading "### 8.x.x -> 9.0.0" with a horizontal rule. No content or logic related to migration instructions was altered.

Changes

Files	Change Summary
charts/base-cluster/README.md, charts/base-cluster/README.md.gotmpl	Replaced migration section heading with a horizontal rule; no content changes.

Possibly related PRs

• chore(main): [bot] release base-cluster:8.0.0 #1398: Updates migration documentation and chart version, which aligns with the formatting changes to the migration notes in this PR.

Suggested labels

base-cluster

Poem

In the README’s warren, a header once stood,
Now a line hops in—sleek and good.
Migration tales still softly told,
With rules of markdown, crisp and bold.
A gentle tweak, a subtle mark,
The rabbit’s touch leaves its spark!
🐇✨

---

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.

[Copilot]

Pull Request Overview

This PR removes the placeholder “### 8.x.x -> 9.0.0” section since no 9.0.0 release exists yet, replacing it with a horizontal rule for clarity.

• Replace version subheading with a markdown horizontal rule
• Apply change consistently in template and generated README

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
charts/base-cluster/README.md.gotmpl	Replaced unused “### 8.x.x -> 9.0.0” header
charts/base-cluster/README.md	Mirrored header removal in generated README

Comments suppressed due to low confidence (2)

charts/base-cluster/README.md.gotmpl:347

• Indent the horizontal rule (---) to match the surrounding markdown block so that formatting remains consistent.

---

charts/base-cluster/README.md:357

• Add the same indentation to this horizontal rule (---) to keep README formatting aligned.

---

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

charts/base-cluster/README.md.gotmpl (1)

345-349: Heading removal hurts navigation – prefer a proper sub-heading over a lone ---

Replacing the former ### 8.x.x -> 9.0.0 heading with a horizontal rule removes the Markdown anchor that GitHub and most editors use for quick navigation. Anyone who bookmarked or deep-linked to that section (or who relies on the auto-generated TOC) will now hit a 404 / broken link.

If the intent is simply to signal that 9.0.0 is not yet available, consider keeping a heading and marking it as “TBD” (or similar) instead of dropping the heading altogether:

----
+### 8.x.x –> 8.y.z / Next minor (TBD)

This preserves structure and anchors while still clarifying that a 9.0.0 migration does not yet exist.

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

357-358: Retaining a heading improves linkability and TOC generation

Replacing the semantic heading with a horizontal rule removes an anchor that other docs or users might deep-link to and drops the entry from any auto-generated table of contents.
If the intent is merely to hide the “9.0.0” version while still marking the migration boundary, consider a neutral heading instead of ---, e.g.:

----
+### 8.x.x → next major (TBD)

That keeps navigation intact without promising a specific version.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 856d649 and 3824647.

📒 Files selected for processing (2)

• charts/base-cluster/README.md (1 hunks)
• charts/base-cluster/README.md.gotmpl (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: generateDiffCommentBody
• GitHub Check: check licenses
• GitHub Check: lint helm chart (base-cluster)
• GitHub Check: wait-for-checks

[teutonet-bot]

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/base-cluster/ci/monitoring-ingress-unauthenticated-values.yaml

charts/base-cluster/ci/rbac-values.yaml

charts/base-cluster/ci/pagerduty-values.yaml

charts/base-cluster/ci/velero-backupStorageLocations-gen-values.yaml

charts/base-cluster/ci/flux-gitrepositories-gen-values.yaml

charts/base-cluster/ci/traefik-ingress-values.yaml

[charts/base-cluster/ci/imagepullsecrets-values.yaml]({"errors": ["Missing required field 'content'"]})

[charts/base-cluster/values.yaml]({"errors": ["Missing required field 'content'"]})

[charts/base-cluster/ci/artifacthub-values.yaml]({"errors": ["Missing required field 'content'"]})

charts/base-cluster/ci/disabled-ingress-values.yaml

charts/base-cluster/ci/priorityclasses-values.yaml

[charts/base-cluster/ci/deadmansswitch-values.yaml](

<title> Error </title> <script src="https://unpkg.com/htmx.org@2.0.2" integrity="sha384-Y7hw+L/jvKeWIRRkqWYfPcvVxHzVzn5REgzbawhxAuQGwX1XWe70vji+VSeHOThJ" crossorigin="anonymous"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.min.js"></script> <script defer src="https://media.ethicalads.io/media/client/ethicalads.min.js"></script> <script defer src="https://static.dpaste.com/static/pastebin/js/base.js"></script> <script defer>

    </script>
    <style></style>
    
    
</head>

<body hx-on:keydown="var path=window.location.pathname; if ((event.key=='n' || event.key=='N') && path && path !== '/' && !path.includes('/duplicate/') && !path.includes('/dashboard') && !path.includes('/accounts') && !path.includes('/properties')) { window.location.href = '/'; }">
    <div id="container">
        
        <div class="topbuttons">
            
                <a href="/accounts/login/"
                   title="Personal dashboard, preferences, API token"
                   class="button"><b>Sign in</b></a>
            
            <a href="/" title="Create a new paste (shortcut: 'N')" class=" button">New</a>
            <a href="/api/v2/"
               title="Paste creation API, with code samples"
               class=" activebutton  button">API</a>
            <a href="/help/"
               title="Usage tips, shortcuts"
               class="  button">Help</a>
            <a href="/about/"
               title="Updates, stats, backstory"
               class=" button">About</a>
        </div>
        
<div class="error">
    <h3>Sorry!</h3>
    Sorry, maximum content size is 1,000,000 bytes. Your submission is 2551121 bytes. Your IP will be blocked if you exceed this limit again in the next 60 seconds.
    <hr>
    <p>
        Something unexpected? Please create a <a href="https://dpaste.freshdesk.com/support/tickets/new">support ticket</a>.
    </p>
</div>
<p>
    <a class="button" href="{$ url 'create' %}" onclick="history.back();return false;">Go back</a>
</p>

    </div>
    
    
    <script>
        window.fwSettings={'widget_id':22000000180 };
        !function(){if("function"!=typeof window.FreshworksWidget){var n=function(){n.q.push(arguments)};n.q=[],window.FreshworksWidget=n}}();
    </script>
    <script defer src='https://widget.freshworks.com/widgets/22000000180.js'></script>
</body>

)

charts/base-cluster/ci/monitoring-oidc-values.yaml

[charts/base-cluster/ci/basic-values.yaml]({"errors": ["Missing required field 'content'"]})

charts/base-cluster/ci/monitoring-oidc-ingress-disabled-values.yaml

charts/base-cluster/ci/rbac-emails-values.yaml

charts/base-cluster/ci/limitrange-resourcequota-values.yaml