Repository navigation
chore(deps): caddy 2.11.4 -> 2.11.7, vaultwarden 1.37.3 -> 1.37.4 - #1022
Merged
Merged
Conversation
Ahead of Sunday's Dependabot run, because the first CVE scan (#852) flagged both. Caddy faces the internet and had 17 fixable HIGHs, all in the Go toolchain it was built with (#973). Vaultwarden had 3 fixable CRITICALs in Debian's perl-base (#1007). Caddy moves in all four stacks that pin it (lab, observability, sensitive, wiki), so the shared pins stay identical. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The intended image upgrades are complete, consistent, and correctly digest-pinned.
Review effort: Balanced
Findings: None
What changed in this PR
Updates vulnerable Caddy and Vaultwarden images to patched, digest-pinned releases.
Changes:
- Updates Caddy to 2.11.7 consistently across four stacks.
- Updates Vaultwarden to 1.37.4 in the sensitive stack.
| File | Description |
|---|---|
stacks/wiki/compose.yaml |
Updates the Caddy pin. |
stacks/sensitive/compose.yaml |
Updates Caddy and Vaultwarden pins. |
stacks/observability/compose.yaml |
Updates the Caddy pin. |
stacks/lab/compose.yaml |
Updates the Caddy pin. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Oct 7, 2026
Closed
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.
Ahead of Sunday's Dependabot run, because the first CVE scan (#852) flagged both images.
What
caddy0c99453…)f2a1290…)vaultwarden/server1587c45…)efb3cde…)stdlib, 3 ingrpcand 3 ingolang.org/x/*. It is bumped in all four stacks together, so the shared-config pins stay identical.perl-base.The next weekly scan rescans both images. It closes their two issues (#973, #1007) itself if the new digests come back clean, or rewrites them to show what is left.
Not in this PR
postgres:18.6andpostgres:17.11drifted again today. Upstream rebuilt them a second time after #966. I reverted that re-pin out of this PR to keep it to the two bumps. Monday'sdigests.ymlwill report it.Deploy note
Merging this is a deploy. Converge recreates Caddy and Vaultwarden on trinity, so every sensitive-tier site served through Caddy restarts briefly. The lab, observability and wiki stacks take the new Caddy on their next
make up.Verification
make pin-digestsresolved both digests from the registry, andmake check-digestsreports every image pinned.make validatepasses everything this change touches, including the Caddyfile checks run againstcaddy:2.11.7.main, not caused by this PR: two ADRs are both numbered 0082, and the README's ADR count is one short.🤖 Generated with Claude Code