Repository navigation
Rebuild fresh NGINX images with HTTP tests and a security gate - #101
Merged
Merged
Conversation
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.
Purpose
Weekly fresh-parent rebuilds and Alpine package refreshes keep all three amd64 variants current. Builds deliberately avoid layer cache so package refreshes actually run.
Fresh-parent baseline (Grype 0.121.3): 1 critical, 3 high, 4 medium matches. Updating zlib 1.3.2-r1 → 1.4-r0 and libxslt 1.1.43-r3 → 1.1.43-r4 removes CVE-2026-4738, CVE-2026-125350, CVE-2026-87636, CVE-2026-9947 and CVE-2025-10911. All three local candidate scans have only 3 medium matches: CVE-2025-60876 in busybox/busybox-binsh/ssl_client (no fix reported); these remain visible in reports.
Local amd64 builds and all three config/HTTP suites passed; template regeneration has no extra diff. No images published. Scheduled/master publication still requires the existing Docker Hub secrets and successful tests/scan.
Closes #4