userpatches: skip jammy in items-from-inventory#460
Merged
igorpecovnik merged 1 commit intomainfrom May 4, 2026
Merged
Conversation
Add jammy to the four skip-releases arrays in targets-all-not-eos.yaml. The all-userspace, all-userspace-riscv64, all-userspace-armhf and all-cli matrix expansions stop emitting jammy rootfs / image targets, which were failing as of armbian/os run 25293593837. No other change. The release stays available to other targets that opt into it explicitly.
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.
Summary
Add `jammy` to the four `skip-releases` arrays in `userpatches/targets-all-not-eos.yaml`. The matrix expansions for `all-userspace`, `all-userspace-riscv64`, `all-userspace-armhf` and `all-cli` stop emitting jammy rootfs / image targets.
Symptom
Run 25293593837 — jammy targets are failing.
Scope
Only this one file. Other places that reference jammy (templates with `RELEASE: jammy` blocks, `external/*-jammy.conf` configs, Docker base images, workflow dropdowns) are left alone — those can be a separate cleanup if you want to retire jammy more broadly.
Diff
```diff
```
(four occurrences across the file).