contour-maintenance

Files (1)

• SKILL.md

SKILL.md (first lines)

# Contour Maintenance Tasks

## Scope
- **Target**: Contour repository (github.com/projectcontour/contour)
- **Supported Branches**: `main` and release-X.Y branches only
- **Platform**: Linux/macOS only
- **Prerequisites**: Contour repository checked out locally, `gh` CLI, `git`, `go`, `httpie`, `osv-scanner`, `govulncheck` installed

## Global Preconditions (MUST validate before ANY task)

Execute these checks and CONTINUE only if all pass:

```bash
# 1. Verify current directory is Contour repo root
test -f Makefile && test -f versions.yaml && echo "✓ In Contour repo root" || echo "✗ NOT in Contour root"
```

CONTINUE to specific tasks only if all checks pass.

## Critical Warnings

**ALWAYS:**
- Determine Go version by reading from `Makefile` variable `BUILD_BASE_IMAGE` only
- Read `versions.yaml` from `main` branch only
- Create local branches with `chore/` prefix
- Execute git status checks between operations
- Verify tool versions with explicit verification before use

**ONLY:**
- Create branches with format: `chore/release-<VERSION>/bump-<TYPE>-<NEW_VERSION>`
- Use commands listed in task procedures exactly as written

---

## Task: Find out what the latest supported Contour releases are

**What this does**: Lists currently supported Contour releases.

MUST execute exactly:
```bash
echo "Latest available Contour releases are:"
git show main:versions.yaml | yq '.versions[] | select(.supported == "true") | .version'
```

---

## Task: Bump Go Version

**What this does**: Updates Go version in Makefile to latest patch level of current minor version (or user-specified major/minor track).

### Step 1: Gather Release Information (REQUIRED)

MUST execute exactly:
```bash
echo "Available Contour release tracks are:"
(echo main && git show main:versions.yaml | yq '.versions[] | select(.supported == "true") | .version' | sed 's/v//' | cut -d'.' -f1-2 | sed 's/^/release-/')
```

MUST capture the output and present it to user.
MUST ask user: "Which Contour release branch to update? (e.g., 1.33, 1.32, or 'main')"
WAIT for response and CONTINUE once user responds.

### Step 2: Verify Current Go Version (REQUIRED)

Replace `<CONTOUR_VERSION>` with user's choice from Step 1.

MUST execute:
```bash
git checkout release-<CONTOUR_VERSION>
git pull
```

Expected: Branch successfully checked out and up-to-date.
CONTINUE only if git commands succeed.

THEN execute:
```bash
OLD_GO_VERSION=$(grep "BUILD_BASE_IMAGE ?=" Makefile | sed 's/.*golang://' | sed 's/@.*//')
echo "Current Go version: ${OLD_GO_VERSION}"
```

MUST capture and report the OLD_GO_VERSION to user.

### Step 3: Execute Bump (NON-REVOCABLE)

MUST execute:
```bash
go run ./hack/actions/bump-go-version/main.go
```

MUST execute:
```bash
NEW_GO_VERSION=$(grep "BUILD_BASE_IMAGE ?=" Makefile | sed 's/.*golang://' | sed 's/@.*//')
echo "New Go version: ${NEW_GO_VERSION}"
```

Decision point:
- IF output shows same Go version as before: Report "Go version already at latest patch level ${OLD_GO_VERSION} for current track" and STOP
- IF changes detected: Continue to Step 4

### Step 4: Commit Changes (SEQUENTIAL)

Execute this step ONLY if Step 3 showed changes detected.

MUST execute:
```bash
git checkout -b chore/release-<CONTOUR_VERSION>/bump-go-${NEW_GO_VERSION}
```

MUST verify:
```bash
git branch --show-current
```
Expected: Branch name matches `chore/release-<CONTOUR_VERSION>/bump-go-<VERSION>`

THEN execute:
```bash
git add -u
git commit -sm "release-<CONTOUR_VERSION>: Bump to go $NEW_GO_VERSION"

From tsaarni/agent-skills, Apache-2.0.

More from tsaarni/agent-skills