ci: publish the cli extension into 2026/next, not 2026/edge - #237
Merged
Conversation
Every other extension repo publishes 2026 into `next`, and `next` is the feed `avocado install` follows. This one still said `edge`, so avocado-ext-cli 1.0.0-rc.2 and rc.3 landed only in 2026/edge; 2026/next has been serving 0.41.2 since. rc.3 is being republished into 2026/next separately. ext-test.yml built only against 2024, so nothing exercised the 2026 feed before a tag; it gets the matching leg.
There was a problem hiding this comment.
🟢 Approval recommended
The workflow changes are small, YAML-valid, and align the test/release matrices with the intended 2026 publishing feed without introducing risky behavioral changes.
Pull request overview
This PR updates the extension CI workflows so avocado-ext-cli releases for the 2026 distro publish to the next feed (which avocado install follows) and adds a corresponding 2026 build leg in extension CI to catch feed-specific issues before tagging.
Changes:
- Switch the 2026 extension release leg from
2026/edgeto2026/next. - Add an
ext-test.ymlmatrix entry to build the extension against2026/next(qemux86-64) in CI.
File summaries
| File | Description |
|---|---|
| .github/workflows/ext-test.yml | Adds a 2026/next build leg to validate the extension against the feed targeted by the 2026 release workflow. |
| .github/workflows/ext-release.yml | Changes the 2026 release channel from edge to next so tagged releases reach users following next. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
lee-reinhardt
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
ext-release.ymlpublishesavocado-ext-cliinto2026/edgewhile every other extension repo — and this repo's own 2024 leg — publishes intonext.nextis the feedavocado installfollows, so the last two CLI releases never reached the users of the 2026 feed:ext-test.ymlbuilt only against 2024 (x86-64 and arm64), so nothing exercised the 2026 feed before a tag went out.How
The 2026 release leg targets
next.ext-test.ymlgains the matching2026/nextleg on qemux86-64, so both feeds the release publishes into are built before a tag.Results
rc.3 was republished into
2026/nextby dispatching this branch's workflow (run 33794740049) — "Published avocado-ext-cli-1.0.0-rc.3; ingest queued". The 2024 leg of that dispatch failed as expected: rc.3 is already published there, and the server rejects a duplicate version ("that extension version is already taken").rc.2 is left where it is; it is superseded.