Skip to content

Correct the reason for the release-only SDK image tag - #3

Merged
jetm merged 1 commit into
mainfrom
misc-1112/fix-sdk-tag-claim
Nov 19, 2026
Merged

jetm merged 1 commit into
mainfrom
misc-1112/fix-sdk-tag-claim

Conversation

@jetm

@jetm jetm commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

Problem

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 avocadolinux/sdk:2026-edge are published on Docker Hub, and meta-avocado's dev feed scripts build the image name from release and channel. Only the -next and -stable tags return 404. @lee-reinhardt pointed this out while reviewing a README draft.

Solution

Say what is true and keep the rule. next is the channel these workflows pass, and the release-only tag resolves on every channel, so the image line stays as it is.

Key changes

  • avocado.yaml: the comment above sdk.image.
  • README.md: the SDK image convention bullet.

Reviewer notes

Comments and prose only; the sdk.image line is unchanged. I checked the tags with the Docker Hub API: 2024, 2026, 2024-edge and 2026-edge return 200, while 2024-next, 2026-next, 2024-stable and 2026-stable return 404. The README bullet below this one still says the feed today is 2024/edge-next, which does not match the workflows (they pass next). I left it for a separate change.

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.

@mobileoverlord mobileoverlord left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. Confirmed on Docker Hub: 2024, 2026, 2024-edge and 2026-edge are 200; 2024-next and 2026-next are 404. I will fix the stale 2024/edge-next feed line in a follow-up, along with a 2026 CI row.

@jetm
jetm merged commit a4f976c into main Nov 19, 2026
1 check passed
@jetm
jetm deleted the misc-1112/fix-sdk-tag-claim branch November 19, 2026 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants