Tracks github.com/rancher/* version drift between rancher/rancher and rancher/webhook across Rancher alpha and Prime head builds.
The scheduled action runs three times a day (02, 10, 18 UTC). For each active v2.X release line it discovers the newest immutable alpha and Prime head images from the last 30 days, then writes a report for every build it has not already processed. Reports live under reports/.
Prime head labels use a seven-character SHA on this page; open a report for the full tag and revision details.
| Line | Stream | Latest build | Status | Webhook | Checked | Report |
|---|---|---|---|---|---|---|
| v2.16 | prime-head |
v2.16.0-cde38be-head |
v0.12.1-rc.3 |
2026-08-29 | open | |
| v2.15 | prime-head |
v2.15.2-fbf2130-head |
v0.11.1 |
2026-08-28 | open | |
| v2.15 | alpha |
v2.15.1-alpha1 |
v0.11.1-rc.1 |
2026-08-19 | open | |
| v2.14 | prime-head |
v2.14.6-d668af0-head |
✅ Clean | v0.10.10 |
2026-08-29 | open |
| v2.14 | alpha |
v2.14.5-alpha1 |
✅ Clean | v0.10.10-rc.2 |
2026-08-19 | open |
| v2.13 | prime-head |
v2.13.10-1256b7b-head |
✅ Clean | v0.9.8 |
2026-08-29 | open |
| v2.13 | alpha |
v2.13.9-alpha1 |
✅ Clean | v0.9.8-rc.2 |
2026-08-19 | open |
| v2.12 | prime-head |
v2.12.14-3af2829-head |
v0.8.9 |
2026-08-28 | open | |
| v2.12 | alpha |
v2.12.13-alpha1 |
v0.8.9 |
2026-08-19 | open | |
| v2.11 | prime-head |
v2.11.18-f3c0ff5-head |
v0.7.10 |
2026-08-28 | open | |
| v2.11 | alpha |
v2.11.17-alpha1 |
v0.7.10 |
2026-08-19 | open | |
| v2.10 | alpha |
v2.10.12-alpha1 |
v0.6.12 |
2026-05-22 | open |
- 2026-08-29 ·
prime-head·v2.16.0-cde38be-head·⚠️ 4 mismatches - 2026-08-29 ·
prime-head·v2.13.10-1256b7b-head· ✅ Clean - 2026-08-29 ·
prime-head·v2.14.6-d668af0-head· ✅ Clean - 2026-08-28 ·
prime-head·v2.16.0-2f60c05-head·⚠️ 4 mismatches - 2026-08-28 ·
prime-head·v2.11.18-f3c0ff5-head·⚠️ 5 mismatches - 2026-08-28 ·
prime-head·v2.14.6-b18f4aa-head· ✅ Clean - 2026-08-28 ·
prime-head·v2.15.2-fbf2130-head·⚠️ 2 mismatches - 2026-08-28 ·
prime-head·v2.12.14-3af2829-head·⚠️ 4 mismatches - 2026-08-28 ·
prime-head·v2.16.0-5779d13-head·⚠️ 4 mismatches - 2026-08-28 ·
prime-head·v2.12.14-b09edb7-head·⚠️ 4 mismatches
Need a one-off check (for example an RC, an older alpha, or an immutable SHA-qualified head)? Add it as a bullet between the markers below — one image tag 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. Do not queue a moving alias such as v2.14-head.
- Discover. Rancher image registries are searched for immutable alpha tags (
vX.Y.Z-alphaN), while Prime head tags (vX.Y.Z-{SHA}-head) are read only fromstgregistry.suse.com. The newest image per release line and stream is selected by imagecreatedtime. For Prime heads,Zis the highest validated numeric patch currently published for that line. Moving aliases such asheadandvX.Y-headare deliberately ignored so a report always identifies one build. A staging outage fails Prime-head discovery instead of silently falling back to a Community registry. - Resolve source. Community images identify the public Rancher commit with
org.opencontainers.image.revision. Prime images have a separate wrapper revision, so Ranch Hand usesorg.opencontainers.image.oss.revisionfor the publicrancher/ranchersource and records both revisions. The SHA embedded in a Prime head tag must match the corresponding prefix of that full OSS revision (legacy 40-character tags match it in full). - Process. For each candidate, the action downloads the resolved public Rancher commit and reads the webhook pin from its
build.yaml, then runsscripts/compare-gomodagainst bothgo.modfiles.build.yamlremains the source of truth because Prime image environments may omit the webhook pin. - Classify.
replacedirectives are applied so the comparison is against effective versions, not rawrequirepins.pkg/apisandpkg/clientdrift is expected (rancher replaces them locally) and is filtered out of the mismatch count. - Index. After every run, the dashboard table above and the per-line index pages in
reports/are regenerated from the on-disk reports. Alpha and Prime head streams remain separate. Nothing else in this README is touched.
Historical reports (pre-2026-04, plaintext format) live in archieve/. They are not regenerated — treat them as a read-only record.