{{ message }}
Repository navigation
fix(ci) - remove debian:11 from CI test matrices (EOL) - #1736
Merged
Abdurrahmaan Iqbal (abdurriq) merged 3 commits intoSep 16, 2026
Merged
Abdurrahmaan Iqbal (abdurriq) merged 3 commits into
Abdurrahmaan Iqbal (abdurriq) merged 3 commits into
Conversation
Venkumahanti Subhankar (V-Subhankar-infy)
requested a lite review from Copilot
September 9, 2026 11:04
Copilot started reviewing on behalf of
Venkumahanti Subhankar (V-Subhankar-infy)
September 9, 2026 11:05
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The change cleanly removes an EOL base image from CI matrices without leaving any dangling exclude references or altering feature support.
Pull request overview
This PR updates the GitHub Actions CI test matrices to stop running Feature tests on debian:11, which is now EOL and causes deterministic apt-get update failures due to expired release metadata.
Changes:
- Removed
debian:11from thebaseImagematrix in the PR workflow (test-pr.yaml). - Removed
debian:11from thebaseImagematrix in the full test workflow (test-all.yaml). - Kept existing matrix
exclude:entries intact (none referenceddebian:11).
File summaries
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.
Venkumahanti Subhankar (V-Subhankar-infy)
marked this pull request as ready for review
September 10, 2026 02:49
Venkumahanti Subhankar (V-Subhankar-infy)
requested a review
from a team
as a code owner
September 10, 2026 02:49
Venkumahanti Subhankar (V-Subhankar-infy)
marked this pull request as draft
September 15, 2026 10:17
Venkumahanti Subhankar (V-Subhankar-infy)
force-pushed
the
fix-stale-variants
branch
from
September 15, 2026 12:22
7983908 to
7087c1d
Compare
Kaniska (v-Kaniska244)
marked this pull request as ready for review
September 15, 2026 13:55
Abdurrahmaan Iqbal (abdurriq)
approved these changes
Sep 16, 2026
Abdurrahmaan Iqbal (abdurriq)
merged commit Sep 16, 2026
f3ca13b
into
devcontainers:main
41 checks passed
Daniel Glaser (the78mole)
added a commit
to the78mole/features
that referenced
this pull request
Sep 19, 2026
The add-groups scenario pinned debian:bullseye. Debian 11 is end-of-life and its security pool is no longer served, so the scenario now fails while installing sudo/git/gnupg2: E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/ main/s/sudo/sudo_1.9.5p2-3+deb11u4_amd64.deb Upstream removed debian:11 from the CI matrices for this reason (devcontainers#1736); this was the last reference left in the repository. Switched to debian:trixie, already the most used Debian image in this scenario file. Nothing in add-groups.sh is release-specific. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Abdurrahmaan Iqbal (abdurriq)
pushed a commit
that referenced
this pull request
Sep 25, 2026
* Initial plan * Add ohMyZshTheme option to common-utils feature Co-authored-by: the78mole <7723396+the78mole@users.noreply.github.com> * Add test scenario for custom zsh theme Co-authored-by: the78mole <7723396+the78mole@users.noreply.github.com> * Add validation for theme name to prevent injection attacks Co-authored-by: the78mole <7723396+the78mole@users.noreply.github.com> * Bump version from 2.5.7 to 2.5.8 * Add support for additional non-root user groups in common-utils feature * Bump version to 2.6.0 in devcontainer feature * "Add/update ko-fi sponsorship to $KOIFI" * Fix FUNDING.yml: ko-fi -> ko_fi (underscore) * common-utils: drop stray FUNDING.yml, bump to 2.7.0 The FUNDING.yml was added to this fork by accident and never belonged in PR #1564. It was malformed anyway — the first line held two U+FFFD replacement characters left over from an unexpanded shell variable. Upstream carries no FUNDING.yml, so the file is simply removed. Bump common-utils 2.6.0 -> 2.7.0: upstream released `sudoers` as 2.6.0, while this fork's 2.6.0 already carried `ohMyZshTheme` and `addGroups`. After the merge the same version number would describe two different option sets, so the merged feature needs its own version. * test(common-utils): move add-groups scenario off EOL debian:11 The add-groups scenario pinned debian:bullseye. Debian 11 is end-of-life and its security pool is no longer served, so the scenario now fails while installing sudo/git/gnupg2: E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/ main/s/sudo/sudo_1.9.5p2-3+deb11u4_amd64.deb Upstream removed debian:11 from the CI matrices for this reason (#1736); this was the last reference left in the repository. Switched to debian:trixie, already the most used Debian image in this scenario file. Nothing in add-groups.sh is release-specific. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * test(common-utils): use debian:bookworm for add-groups scenario Follow-up to the previous commit, which moved the scenario off EOL debian:bullseye to debian:trixie. A maintainer asked for bookworm (12) in review, so use that instead: #1564 (review comment on scenarios.json:139) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Kaniska <kaniska244@github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 PR touching any Feature gets red
test (<feature>, debian:11)and bullseyetest-scenariosjobs.Debian 11 reached EOL on 2026-08-31. Its security archive stopped being re-signed that day, and APT release files are valid for 7 days, so the metadata expired on 2026-09-07. Feature
install.shscripts run underset -eand install apt prerequisites first, so every Feature fails identically. This is permanent, not a flake; re-running will not help.Verified 2026-09-09:
Change
CI matrices: removes
"debian:11"from thebaseImagematrix intest-pr.yamlandtest-all.yaml(noexclude:entries referenced it).test-pr-arm64.yamlalready excluded debian:11 and anticipated this EOL date, so this just makes the amd64 matrices consistent with it.Test scenarios: clears the 14 remaining bullseye/
debian:11pins across 7 Features that run intest-scenarios. Bullseye-only scenarios and their test scripts are removed (anaconda, common-utils, git); the rest are retargeted to bookworm/debian:12(azure-cli, common-utils, java, node, python).This drops CI coverage of an EOL image only. No Feature drops Debian 11 support: no
install.sh, nodevcontainer-feature.json, and no Feature version is touched.Alternatives considered
•
Acquire::Check-Valid-Until=false: disables APT freshness and signature checks repo-wide to paper over an EOL image.•
archive.debian.org: keeps CI validating an unsupported distro, and the host is rate-limited and unsuited to CI load.• Nothing: the jobs are
continue-on-error: true, so they don't block merges — but every PR still burns a full matrix leg on a guaranteed failure, and a standing red X hides real regressions in those same jobs.