diff --git a/docs/DEPLOYMENTS.md b/docs/DEPLOYMENTS.md index 9e80eea1f..a002ba1f1 100644 --- a/docs/DEPLOYMENTS.md +++ b/docs/DEPLOYMENTS.md @@ -18,9 +18,9 @@ The current GHCR channel tag set is: | Channel | Tags | | --- | --- | -| Stable | `latest`, `latest-omnibus`, `latest-web`, `latest-collector`, `latest-collector-zfs`, `latest-collector-mdadm`, `latest-collector-btrfs`, `latest-collector-performance` | -| Beta | `beta`, `beta-omnibus`, `beta-web`, `beta-collector`, `beta-collector-zfs`, `beta-collector-mdadm`, `beta-collector-btrfs`, `beta-collector-performance` | -| Testing | `develop`, `develop-omnibus`, `develop-web`, `develop-collector`, `develop-collector-zfs`, `develop-collector-mdadm`, `develop-collector-btrfs`, `develop-collector-performance` | +| Stable | `latest`, `latest-omnibus`, `latest-web`, `latest-collector`, `latest-collector-omnibus`, `latest-collector-zfs`, `latest-collector-mdadm`, `latest-collector-btrfs`, `latest-collector-performance` | +| Beta | `beta`, `beta-omnibus`, `beta-web`, `beta-collector`, `beta-collector-omnibus`, `beta-collector-zfs`, `beta-collector-mdadm`, `beta-collector-btrfs`, `beta-collector-performance` | +| Testing | `develop`, `develop-omnibus`, `develop-web`, `develop-collector`, `develop-collector-omnibus`, `develop-collector-zfs`, `develop-collector-mdadm`, `develop-collector-btrfs`, `develop-collector-performance` | The legacy `master-omnibus`, `master-web`, and `master-collector` tags still resolve in GHCR but are frozen legacy images. They are not generated by current workflows. There is no `testing` tag. diff --git a/docs/TROUBLESHOOTING_DOCKER.md b/docs/TROUBLESHOOTING_DOCKER.md index 44a1e402b..ac18788a6 100644 --- a/docs/TROUBLESHOOTING_DOCKER.md +++ b/docs/TROUBLESHOOTING_DOCKER.md @@ -10,6 +10,10 @@ Scrutiny uses two branch-backed image channels and one release-backed stable cha - `beta` branch -> `beta` and `beta-omnibus` - release tag -> `latest` and `latest-omnibus` +Each channel also publishes one tag per image in `docker/image-matrix.json`, such as +`develop-collector-omnibus` or `latest-collector`. The full set is in +[DEPLOYMENTS.md](DEPLOYMENTS.md#published-channel-tags). + Direct pushes to `master` do not publish stable images. Release tags are the only source for `latest` tags. Typical flow is `develop -> master`, with optional `develop -> beta -> master` promotion when a feature needs pre-release validation.