Repository navigation
CI: cover 2026/next as well as 2024/next - #5
Open
mobileoverlord wants to merge 1 commit into
Open
mobileoverlord wants to merge 1 commit into
mobileoverlord wants to merge 1 commit into
Conversation
Contributor
Author
qemux86-64 is published on the 2026 feed now, and every bsp-*/ext-* repo starts from this template, so new repos should cover both releases. The README's feed line said 2024/edge-next, which the workflows never used.
mobileoverlord
force-pushed
the
jschneck/ci-2026-row
branch
from
November 19, 2026 19:48
27ddfa2 to
2aff4aa
Compare
Contributor
|
@mobileoverlord #4 is merged. You can rebase now |
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
Every
bsp-*andext-*repo starts as a copy of this template, but its Test and Release workflows only run on 2024/next. A new repo therefore starts without 2026 coverage and needs a follow-up to add it. The README's feed bullet also said2024/edge-next, a channel the workflows never pass, and that the 2026 feed carries onlyjetson-agx-thor.Solution
test.ymlandrelease.yml: add theqemux86-642026/next leg. qemux86-64 is published on 2026/next and 2026/edge.test.yml: the header comment now says one leg per release, dropped only when a target isn't published there.README.md: replace the stale feed bullet with what the workflows do.Reviewer notes
Follow-up to #3, which left the feed bullet for a separate change. This PR's own Test run exercises the new 2026 leg.