ci: drop debian-11 (EOL), add debian-13 testing - #2131
Open
twangboy wants to merge 2 commits into
Open
Conversation
Debian 11 (bullseye) reached the end of its LTS window on 2026-08-31 (https://www.debian.org/releases/bullseye/). Its security suite is now frozen (Release file's own Date field is stuck at that exact moment) and packages are becoming unreliable to fetch - this has been repeatedly breaking salt-ci-containers' testing:debian-11 image build, in turn blocking publication of every other image in the same run (fail-fast: false doesn't help here since the downstream merge/publish job still needs every build job to succeed). Salt's own published support policy already excludes this case: 'Debian stable, oldstable, and oldoldstable (if it is not EOL) versions.' Debian 11 is oldoldstable and is now EOL, so it falls outside Salt's own supported list. Follows the same pattern as the debian-10 removal (69495e9): drop the CI job and bump __check_end_of_life_versions' Debian threshold from <11 to <12, matching the same hard-block convention already used for other EOL distros (e.g. ALT Linux's <10 check). debian-13 was already scaffolded in generate.py (its git-version blacklist entries were pre-populated, just commented out of the base distro lists) - move it from commented to active in LINUX_DISTROS/ STABLE_DISTROS/ONEDIR_DISTROS so Debian keeps CI coverage. Its existing blacklist entries correctly keep it out of git-3006/git-3007/ git-master while allowing git-3008, so no further changes were needed there. testing:debian-13's container image already builds successfully in salt-ci-containers, unlike debian-11.
This was referenced Sep 4, 2026
debian-11 was already dropped from LINUX_DISTROS/STABLE_DISTROS/ ONEDIR_DISTROS, so these blacklist and display-name entries were dead weight with no effect on the generated workflow. Confirmed ci.yml is unchanged after regenerating.
3 tasks
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.
What does this PR do?
Debian 11 (bullseye) reached the end of its LTS window on 2026-08-31 (https://www.debian.org/releases/bullseye/). Its security suite is now frozen (the
Releasefile's ownDatefield is stuck at that exact moment) and packages are becoming unreliable to fetch - this has been repeatedly breakingsalt-ci-containers'testing:debian-11image build, which in turn blocks publication of every other image in the same run (the downstreammerge/publish job needs everybuildmatrix entry to succeed, regardless offail-fast: false).Salt's own published support policy already excludes this case: "Debian stable, oldstable, and oldoldstable (if it is not EOL) versions." Debian 11 is
oldoldstableand is now EOL, so it's outside Salt's own supported list - the "Full" entry in the supported-OS table just hasn't caught up to that yet.Changes
debian-11CI job fromci.yml(regenerated via.github/workflows/templates/generate.py)__check_end_of_life_versions's Debian threshold inbootstrap-salt.shfrom< 11to< 12, matching the same hard-block convention already used for other EOL distros (e.g. ALT Linux's< 10check) and following the precedent of the debian-10 removal (69495e9)debian-13testing (LINUX_DISTROS/STABLE_DISTROS/ONEDIR_DISTROSingenerate.py) so Debian keeps CI coverage. It was already scaffolded in - its git-version blacklist entries (excludinggit-3006/git-3007/git-master, allowinggit-3008) were already pre-populated, just commented out of the base distro lists - so no further changes were needed there.testing:debian-13's container image already builds successfully insalt-ci-containers, unlikedebian-11.What issues does this PR fix or reference?
Unblocks the ongoing
testing:debian-11breakage in saltstack/salt-ci-containers (PR #141 there is a retry-based mitigation for the underlying mirror flakiness, but this is the real fix - the distro itself is EOL).