release: avocado-ext-tunnels 0.1.1, published to the next channel - #3
Merged
Merged
Conversation
0.1.0-r1 reached 2024/edge-next (where it did land in every target's ext feed, including imx8mp-evk-ext) and 2026/edge, but never 2026/next -- which is the feed a 2026 project on the next channel resolves against. That is why avocado-ext-tunnels is missing for imx8mp-evk on 2026: not a failed release, but two channels that nothing consumes. Publish to 2026/next and 2024/next instead, matching every extension that does reach those feeds (ext-dev, ext-podman, ext-microclaw, ...). The target stays qemux86-64: the extension RPM is noarch, so one build per release/channel fans out to that channel's per-target ext feeds. Cargo.toml goes to 0.1.1 -- the release workflow guards that the pushed tag equals it -- and the RPM release restarts at r0 for the new version.
The test matrix built against 2024/edge-next only, which release.yml no longer publishes to. A PR could go green without ever having built against either feed the tag ships into. Mirror the release matrix: 2026/next and 2024/next.
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
1 participant
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.
Ships
avocado-ext-tunnelsinto the feeds that projects actually resolve against.Why
0.1.0-r1released fine. It just landed where nothing reads it:qemux86-64-extimx8mp-evk-ext2024/edge-next0.1.0-r10.1.0-r12026/edge0.1.0-r0,-r12026/next0.1.0-r0,-r1A 2026 project on the
nextchannel resolves2026/next/target/<target>-ext, soavocado-ext-tunnelsis simply not there for any target but qemux86-64 — animx8mp-evk project gets nothing to resolve from
source: { type: package }.The target was never the problem. The extension RPM is noarch, so one
qemux86-64build fans out to every target ext feed within itsrelease/channel — which is exactly how
2024/edge-nextended up carrying aworking
imx8mp-evk-extcopy. The channel is the bug.What changed
2026/nextand2024/next, matching every extension thatdoes reach those feeds (
ext-dev,ext-podman,ext-microclaw, …).qemux86-64stays as the build target, for the noarch reason above.Cargo.toml/Cargo.lock→0.1.1. The release workflow guards that thepushed tag equals the Cargo.toml version.
release: r1→r0:r1was a repackage of0.1.0, and the RPM releaserestarts for a new upstream version.
Release
Merge, then from
main:git tag 0.1.1 && git push origin 0.1.1.Not in this PR
version: { file: Cargo.toml, key: package.version }(the localhermetic-ext-version-sourcework). It is orthogonal and matters forsource: { type: path | git }consumers, not for this tag-triggered release.