Add Release Blog Post for KubeDB V2025.5.30

[souravbiswassanto]

No description provided.

[github-actions]

Visit the preview URL for this PR (updated for commit 8d6f375):

https://blog-v1-hugo--pr510-kubedb-v2025-5-30-rp56if2h.web.app

_{(expires Thu, 12 Jun 2025 21:01:39 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: ddacb919f90a98185619681ef0da6429c962b808}

[sheikh-arman]

LGTM

[Evanraisul]

LGTM

[pritamdas99]

LGTM!

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
926438	Triggered	Google API Key	8d6f375	config.dev.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[Copilot]

Pull Request Overview

This PR updates product release metadata for multiple offerings by adding new release entries and updating the latestVersion attribute. Additionally, it updates the search API key in the development configuration.

• Adds release entries for version v2025.5.30 in voyager, kubevault, and kubedb product files.
• Inserts an additional historical release (v2025.5.26) in kubevault and updates the listing to reflect v2025.5.30 as the latestVersion.
• Updates the release entry for configsyncer to version v0.15.3 and adjusts the corresponding latestVersion.
• Modifies the search API key in config.dev.yaml.

Reviewed Changes

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

Show a summary per file

File	Description
data/products/voyager.json	Added new release entry for v2025.5.30 and updated latestVersion.
data/products/kubevault.json	Added new release entries for v2025.5.30 and v2025.5.26; updated latestVersion.
data/products/kubedb.json	Added new release entry for v2025.5.30 and updated latestVersion.
data/products/configsyncer.json	Added new release entry for v0.15.3 and updated latestVersion.
config.dev.yaml	Updated the search API key value.

Comments suppressed due to low confidence (2)

config.dev.yaml:34

• Ensure that the API key included in config.dev.yaml is treated appropriately, especially if the file is publicly accessible.

search_api_key: AIzaSyBrcwLTnL09geNrFMUx1kpL--dT1379aag

data/products/kubevault.json:237

• [nitpick] Confirm that the inclusion and ordering of the v2025.5.26 release entry is intentional relative to the v2025.5.30 release entry for clear version history.

"version": "v2025.5.26",