Repository navigation
Chore/dependency updates - #95
Merged
Merged
Conversation
Composer: symfony/http-foundation, http-kernel, routing, yaml and mime to the patched 7.4.23 / 8.1.11 / 7.4.22 releases (host and path handling, YAML parse time, mime header injection), with the rest of symfony/* and doctrine/deprecations along. composer audit is clean. pnpm: axios 1.21.1 (follow-redirects credential leak), concurrently 9.2.5 (shell-quote command injection), vite 6.4.6 (server.fs.deny bypass). pnpm audit is clean, vite build passes. Backend suite: 541 passed. Co-Authored-By: Claude Mythos 5.1 <noreply@anthropic.com>
The serversideup base image ships gcc, g++, make, binutils, libc6-dev and linux-libc-dev. Nothing needs them at runtime, and linux-libc-dev alone put some fifty kernel CVEs into every weekly Trivy image scan. Purge them after the PHP extensions are built. Checked on a local build: the toolchain is gone, opentelemetry, protobuf, redis and pdo_sqlite still load, artisan boots, and Trivy reports no fixable CRITICAL or HIGH findings (the published :latest has 56). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
:latest was only built when a v* tag was pushed, so between releases it kept the Debian packages of release day and the weekly Trivy image scan went red on fixes published since. The Monday schedule now also checks out the newest final v* tag and rebuilds it with current packages, pushing :latest, :stable and its version tags. Same code and version string as the release, nothing from dev. A workflow_dispatch input runs just this rebuild on demand. The two builds use separate GHA cache scopes so they do not evict each other. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
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
 |
…ing tags The weekly release rebuild pushed straight to :latest and the version tags, and the Trivy scan only looked at it two hours later. Self-hosters who auto-pull :latest would have received a broken or suspicious image first. The job now builds a linux/amd64 candidate and loads it locally, boots it with a production-like env and requires /health to answer 200 and the opentelemetry and protobuf extensions to load, then runs the Trivy gate with today's exceptions file. Only after both pass does it push the multi-platform image, from the cache the candidate build wrote. The rebuild now moves :latest and :stable only. 1.9.1 and 1.9 keep the bytes of their release, so pinning a version means what it says. Co-Authored-By: Claude Opus 5.5 <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.
No description provided.