Prepare for release v2026.6.18-rc.2

[1gtm]

ProductLine: KubeDB
Release: v2026.6.18-rc.2
Release-tracker: kubedb/CHANGELOG#138
Signed-off-by: 1gtm 1gtm@appscode.com

Summary by CodeRabbit

• Documentation
  • Added comprehensive changelog documentation for KubeDB release v2026.6.18-rc.2, documenting updates across multiple subcomponents with linked commit references.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new Markdown file docs/CHANGELOG-v2026.6.18-rc.2.md is added. It contains front-matter metadata (title, description, menu placement, URL, alias) and the full changelog body for KubeDB v2026.6.18-rc.2, organized as per-repository sections with linked commit references and brief change descriptions.

Changes

KubeDB v2026.6.18-rc.2 Changelog

Layer / File(s)	Summary
Changelog front-matter and release notes docs/CHANGELOG-v2026.6.18-rc.2.md	Adds the complete changelog page with front-matter metadata (title, description, menu routing, canonical URL, alias) and the full per-repository release sections listing linked commits and change descriptions for v2026.6.18-rc.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 A changelog hops into the docs with glee,
Each commit a carrot for all to see.
Front-matter in order, the menu aligned,
rc.2 is noted, no bug left behind.
KubeDB blooms fresh like clover in spring! 🌿

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Prepare for release v2026.6.18-rc.2' directly and specifically relates to the main change in the PR, which is adding a changelog documentation file for this exact release version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ 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 v2026.6.18-rc.2-master

---

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

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/CHANGELOG-v2026.6.18-rc.2.md`:
- Around line 25-26: The changelog contains inconsistent commit hash lengths
between the display text and the GitHub URLs. In the entries on lines 25 and 26
(and line 54), the display text shows 8-character commit hashes while the URLs
contain 9-character hashes. Update the display text (the text inside the square
brackets before the URL) for each commit entry to match the 9-character hash
length found in the corresponding GitHub URLs. This ensures consistency and
prevents broken or misleading links.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1fa05d08-5703-41cf-85a5-faa0a1b9c8cd

📥 Commits

Reviewing files that changed from the base of the PR and between 7170308 and e18ddf7.

📒 Files selected for processing (1)

• docs/CHANGELOG-v2026.6.18-rc.2.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Inconsistent commit hash lengths in GitHub URLs may cause broken links.

Multiple commit entries have mismatched hash lengths between the display text (8 characters) and the GitHub commit URL (9 characters). For example:

• Line 25: display text 2309f632 → URL includes 2309f632f
• Line 26: display text 20f0dc78 → URL includes 20f0dc781
• Line 54: display text 4b212df0 → URL includes 4b212df05

Git short commit hashes are typically 7–12 characters, but consistency within a file—especially when linking to the same repositories—is important. Verify that all commit URLs are correct and reachable; if the 9-character form is standard for this repository's changelog generation, standardize the display text to match, or vice versa.

Also applies to: 54-54

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/CHANGELOG-v2026.6.18-rc.2.md` around lines 25 - 26, The changelog
contains inconsistent commit hash lengths between the display text and the
GitHub URLs. In the entries on lines 25 and 26 (and line 54), the display text
shows 8-character commit hashes while the URLs contain 9-character hashes.
Update the display text (the text inside the square brackets before the URL) for
each commit entry to match the 9-character hash length found in the
corresponding GitHub URLs. This ensures consistency and prevents broken or
misleading links.