OpenParable
Skip to content
← Back to skills

Lock Release Docs

DevOps & Security
lock-release-docs

Lock Release Docs is an Agent Skill for devops & security published in the akuity/kargo repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Lock docs and scripts on a release branch to a specific patch version

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/akuity/kargo/blob/HEAD/.claude/skills/lock-release-docs/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/lock-release-docs, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Lock all documentation and scripts on a release branch so they reference a specific version instead of floating references like main or latest.

Arguments: $0 = release branch (e.g. release-1.9), $1 = version to lock to (e.g. 1.9.3)./

Before starting

  1. Fetch from the upstream remote.
  2. Check out $0 and make sure it is up to date with upstream/$0.
  3. Create a working branch (e.g. lock-$0-docs) off of $0.

What to search for

Search docs/ and hack/ thoroughly for the patterns below. Do not assume a fixed set of files -- new docs or scripts may introduce new instances over time.

Floating GitHub URLs pointing at main

Any raw.githubusercontent.com/akuity/kargo/main/... or github.com/akuity/kargo/tree/main/... URL should be updated to reference the release branch instead (e.g. refs/heads/$0 for raw content URLs, tree/$0 for tree links).

Floating GitHub release URLs using latest

Any github.com/akuity/kargo/releases/latest/download/... URL should be pinned to the specific version: releases/download/v$1/....

Kargo Helm chart commands without a version pin

Any helm install, helm upgrade, or helm inspect values command that references oci://ghcr.io/akuity/kargo-charts/kargo without a --version flag needs --version $1 added. Place it on the line immediately after the chart URL, before any --namespace or --set flags, to match the style used by nearby third-party chart installs.

Do not modify helm commands for third-party charts (cert-manager, Argo CD, Argo Rollouts, etc.) -- those manage their own version pins.

After all edits

  1. Summarize every change (file, line, what changed) and present the diff.
  2. Do not commit automatically -- wait for the user to review and approve.