Webhook Ranch Hand

Tracks github.com/rancher/* version drift between rancher/rancher and rancher/webhook on every new Rancher alpha.

The scheduled action runs three times a day (02, 10, 18 UTC), discovers the newest -alpha for each active v2.X release line in the last 30 days, and writes a report for any alpha it hasn't already processed. Reports live under reports/.

Latest per release line

Line	Latest alpha	Released	Status	Webhook	Webhook released	Checked	Report
v2.15	v2.15.0-alpha3	2026-04-14	⚠️ 8 mismatches	v0.10.0	2026-03-18	2026-04-24	open
v2.14	v2.14.1-alpha13	2026-04-29	✅ Clean	v0.10.4-rc.1	2026-04-28	2026-04-30	open
v2.13	v2.13.5-alpha7	2026-04-28	⚠️ 6 mismatches	v0.9.4-rc.1	2026-04-28	2026-04-28	open
v2.12	v2.12.9-alpha7	2026-04-28	⚠️ 5 mismatches	v0.8.6-rc.1	2026-04-28	2026-04-28	open
v2.11	v2.11.13-alpha6	2026-04-28	⚠️ 4 mismatches	v0.7.9-rc.1	2026-04-28	2026-04-28	open

Recent runs

• 2026-04-29 · v2.14.1-alpha13 · ✅ Clean
• 2026-04-29 · v2.14.1-alpha12 · ✅ Clean
• 2026-04-28 · v2.11.13-alpha6 · ⚠️ 4 mismatches
• 2026-04-28 · v2.12.9-alpha7 · ⚠️ 5 mismatches
• 2026-04-28 · v2.13.5-alpha7 · ⚠️ 6 mismatches
• 2026-04-28 · v2.14.1-alpha11 · ✅ Clean
• 2026-04-27 · v2.14.1-alpha8 · ✅ Clean
• 2026-04-24 · v2.11.13-alpha5 · ⚠️ 4 mismatches
• 2026-04-24 · v2.12.9-alpha6 · ⚠️ 5 mismatches
• 2026-04-24 · v2.13.5-alpha6 · ⚠️ 6 mismatches

Manual runs queue

Need a one-off check (e.g. an RC, or an older alpha)? Add it as a bullet between the markers below — one version per line, with a leading v. The next scheduled run will process it and delete the line on success. Failed entries are left in place so they retry automatically.

How it works

1. Discover. gh api /repos/rancher/rancher/releases is filtered to prereleases matching ^v\d+\.\d+\.\d+-alpha\d+$, within the last 30 days, and reduced to the newest alpha per release line.
2. Process. For each candidate, the action downloads rancher/rancher@<tag> and resolves the webhook pin from build.yaml, then runs scripts/compare-gomod against both go.mod files.
3. Classify. replace directives are applied so the comparison is against effective versions, not raw require pins. pkg/apis and pkg/client drift is expected (rancher replaces them locally) and is filtered out of the mismatch count.
4. Index. After every run, the dashboard table above and the per-line index pages in reports/ are regenerated from the on-disk reports. Nothing else in this README is touched.

Archive

Historical reports (pre-2026-04, plaintext format) live in archieve/. They are not regenerated — treat them as a read-only record.