versions-renovate

Generates and validates `# renovate:` annotation syntax for `versions.env` entries.

1|Updated Apr 6, 2025

Search Tags:#kubernetes #gitops #version management #renovate #oci registry #helm charts #annotation syntax

Ready to run

npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill versions-renovate-david-driscoll

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: versions-renovate
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/versions-renovate
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill versions-renovate-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents Renovate from silently skipping version entries by ensuring your versions.env annotations follow the exact syntax and ordering the custom regex manager expects.

Core Features & Use Cases

Correct annotation syntax: Ensures required keys like datasource and depName are present and ordered correctly to avoid ignored entries.
Datasource-appropriate tracking: Differentiates between HTTP Helm charts, OCI Helm registries, and GitHub release/tag sources.
Debugging & container image handling: Covers adding image tag annotations in YAML, handling non-semver versions with versioning=loose, and diagnosing common failure modes.

Quick Start

Ask the AI to generate the exact # renovate: annotation line for a new Helm chart or OCI image version entry you want to add to kubernetes/platform/versions.env, including the correct key order for your datasource.

Frequently Asked Questions about versions-renovate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does Renovate silently skip version entries in my versions.env file?▼

Renovate skips version entries when the `# renovate:` annotation syntax is incorrect. The custom regex manager requires fixed key ordering, proper datasource selection, and exact regex placement to successfully parse and track your Kubernetes component versions.

How do I add a Renovate annotation for an OCI Helm chart in versions.env?▼

To add an OCI Helm chart annotation, you must generate a `# renovate:` line with the correct datasource and depName keys. Differentiating between HTTP Helm charts and OCI Helm registries ensures Renovate selects the proper datasource for tracking.

What's the best way to handle non-semver container image tags with Renovate?▼

Handle non-semver container image tags by applying `versioning=loose` in your Renovate annotation. This prevents parsing failures and ensures Renovate can still track and update image tags that do not follow standard semantic versioning rules.

Does Renovate support tracking GitHub releases and tags alongside Docker images in the same file?▼

Yes, Renovate supports tracking GitHub releases, GitHub tags, and Docker images in the same file. You must specify the correct datasource—github-releases, github-tags, or docker—in each annotation to ensure Renovate parses every entry correctly.

How do I fix Renovate annotation syntax for Kubernetes homelab version tracking?▼

Fix Renovate annotation syntax by ensuring required keys like `datasource` and `depName` are present and ordered exactly as the custom regex manager expects. Validating against the expected key order prevents Renovate from ignoring your homelab version entries.

When do I need to use different Renovate datasources for Helm charts?▼

You need different Renovate datasources when tracking Helm charts from HTTP sources versus OCI registries. Selecting the correct helm or docker datasource ensures the annotation matches the registry type and allows Renovate to properly fetch chart updates.