From 6d6903be71bba59c97774e4e320733e046bba5f1 Mon Sep 17 00:00:00 2001 From: Javier Tia Date: Thu, 19 Nov 2026 12:55:45 -0600 Subject: [PATCH] Correct the reason for the release-only SDK image tag The avocado.yaml comment and the README both say a channel-suffixed SDK image tag does not exist for any release. That is wrong: avocadolinux/sdk:2024-edge and 2026-edge are published, and meta-avocado's dev feed scripts build the image name from release and channel. Only the -next and -stable tags return 404. State that, and keep the rule: next is the channel these workflows pass, so the release-only tag is the one that resolves on every channel. Comments and prose only; the image line is unchanged. --- README.md | 6 ++++-- avocado.yaml | 5 +++-- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 83f39af..21d0773 100644 --- a/README.md +++ b/README.md @@ -26,8 +26,10 @@ Release: tag the commit with the exact `avocado.yaml` version, e.g. `git tag 0.1 - **SDK image is release-scoped, not channel-scoped.** `docker.io/avocadolinux/sdk:{{ env.AVOCADO_DISTRO_RELEASE }}` → `avocadolinux/sdk:2026` on a 2026 CI leg, `avocadolinux/sdk:2024` on a 2024 one. Do not append - `-{{ env.AVOCADO_DISTRO_CHANNEL }}` — there is no such tag on any release. The channel - selects the *package feed*; the image tag is per-release only. + `-{{ env.AVOCADO_DISTRO_CHANNEL }}`. Channel-suffixed tags exist for some channels + only (`2024-edge` and `2026-edge` are published, `-next` is not), and `next` is the + channel the workflows here use. The release-only tag resolves on every channel. The + channel selects the *package feed*. - **CI comes from `avocado-linux/actions@v1`**, pinned. The matrix lives in the caller so each repo owns its own target/feed combinations. - **Feed today is `2024`/`edge-next`.** `avocado-linux/actions@v1` *defaults* to diff --git a/avocado.yaml b/avocado.yaml index dc5de79..97c95f5 100644 --- a/avocado.yaml +++ b/avocado.yaml @@ -29,7 +29,8 @@ extensions: # nativesdk-foo: '*' # Release-scoped, not channel-scoped: this resolves to avocadolinux/sdk:2026. -# The SDK image is per-release only — appending the channel points at a tag -# that does not exist. +# Do not append the channel: tags such as -edge exist for some channels only, +# and there is no -next tag, the channel the workflows here use. The +# release-only tag resolves on every channel. sdk: image: docker.io/avocadolinux/sdk:{{ env.AVOCADO_DISTRO_RELEASE }}