Repository navigation
Repair wp/7.1 branch Actions: Point the bullseye security apt sources at archive.debian.org - #85485
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
🤖 PR meta 🤖📦 Bundle sizeSize Change: 0 B Total Size: 7.75 MB
|
… of dropping them.
7a6f433 to
675661a
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
Part of #82781.
What?
Backports #85469 to this branch's
wp-env: thebullseye-securityapt sources of the bullseye-based WordPress images (PHP 7.3, 7.4, and 8.0) now point atarchive.debian.orginstead of being deleted.Why?
When #82478 was written,
bullseye-securitywas not onarchive.debian.orgyet, so it was dropped rather than rewritten. That change is already on this branch. The archive has served the suite since 2026-09-12 (http://archive.debian.org/debian-security/dists/bullseye-security/Release). While the suite is dropped, images built bywp-envinstall packages without Debian's security updates. For example,libc6resolves to2.31-13+deb11u11frombullseyeinstead of2.31-13+deb11u14frombullseye-security.This was raised in review of the
wp/6.9backport of #82478 (#82873 (comment)). The same fix was added to thewp/7.0throughwp/6.3stacks in the pull requests that already handle the bullseye apt sources.wp/7.1has no such pull request, because #82478 was already on the branch (3b49e92). #85469 will not be backported towp/7.1now thatwp/7.2exists, so this pull request adds the fix to the stack, in the same position as the bullseye pull requests on the other branches: abovepin-runner-images(#82792) and belowpin-wp-env-core-version(#82791).How?
Same change as #85469 in
packages/env/lib/runtime/docker/docker-config.js:/bullseye-security/ddeletion with two rewrites, matching how the stretch and buster security suites are already handled. Both are needed because the images do not agree on the host:wordpress:php7.3usessecurity.debian.org/debian-security, andwordpress:php7.4andwordpress:php8.0usedeb.debian.org/debian-security.bullseye-updatesis still dropped, asbuster-updatesandstretch-updatesare.Testing Instructions
.wp-env.jsonthat sets"phpVersion": "7.3", runnode /path/to/gutenberg/packages/env/bin/wp-env startusing this branch's checkout. Repeat with"7.4"and"8.0".apt-geterrors.node /path/to/gutenberg/packages/env/bin/wp-env run cli cat /etc/apt/sources.listand confirm thebullseye-securityline points atarchive.debian.org/debian-security.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.
🤖 Generated with Claude Code