Repository navigation
Vary the release matrix by feed, not by target - #3
Merged
Merged
Conversation
The 0.1.0 release published qemux86-64 successfully and then failed on imx93-frdm with "that extension version is already taken". Both rows targeted 2024/next, and an extension version is global within a distro release and channel, so the second row was a duplicate publish rather than a second target. Per-target rows buy nothing to lose. Connect distributes a published extension to the per-target feeds itself: avocado-ext-cli and avocado-ext-microclaw both ship architecture-specific binaries, both publish only a qemux86-64 row, and both are present in imx93-frdm-ext as well as qemux86-64-ext. So the target input names the target used to package, not the set of devices that can install the result. Varying release and channel instead also covers what the per-target matrix never did: 0.1.0 only ever reached 2024/next, leaving 2026/next without the extension at all. Both feeds now get every release. The version moves to 0.1.1 because 0.1.0 is taken in 2024/next and the publish is refused on a collision rather than overwriting. Re-tagging 0.1.0 would fail the 2024 leg for the same reason it failed the first time. Signed-off-by: Javier Tia <javier@peridio.com>
nicksinas
approved these changes
Sep 15, 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.
Problem
The 0.1.0 release published
qemux86-64and then failed onimx93-frdmwiththat extension version is already taken. Both rows pointed at2024/next, and anextension version is global within a distro release and channel, so the second row
was a duplicate publish rather than a second target.
Solution
Vary release and channel instead. Connect distributes a published extension to the
per-target feeds itself -
avocado-ext-cliandavocado-ext-microclawboth shiparchitecture-specific binaries, both publish only a
qemux86-64row, and both arepresent in
imx93-frdm-extas well asqemux86-64-ext- so thetargetinputnames the target used to package, not the set of devices that can install the result.
This also fixes coverage the per-target matrix never had: 0.1.0 reached
2024/nextonly, leaving
2026/nextwithout the extension entirely.Verification
Tag 0.1.1 published successfully to both feeds:
Reviewer notes
2024/nextand a collisionis refused rather than overwritten, so re-tagging 0.1.0 would fail the 2024 leg
again.
supported_targetsstill declaresqemux86-64andimx93-frdm. That list iswhat the extension supports; it is not the publish matrix, and the two should not
be kept in step.
main-mainis protected, so the fix went out as a tag before it could land here.Merging this reconciles them.