Repository navigation
chore(sensitive): Immich v3.2.4 -> v3.3.1, ahead of Sunday's Dependabot (#979) - #1129
Merged
Merged
Conversation
…ot (#979) The weekly scan flagged immich-server v3.2.4 (#979). With the pinned trivy, --ignore-unfixed, HIGH/CRITICAL, today's database: v3.2.4 is 4 critical / 48 high, v3.3.1 is 4 critical / 34 high. Debian's gzip, sqlite and openssl and npm's compression, multer and sharp are fixed. What remains (proxy-addr, tar, brace-expansion, fast-uri, undici, ws and others) is transitive npm inside upstream's build, so #979 stays open until Immich ships a clean one. Machine learning moves with it because the two must match, not for its CVEs: v3.3.1 rebased onto a newer Debian and scans 4 critical / 27 high against v3.2.4's 4 / 26. #978 carries that triage. Neither release note lists a breaking change, and upstream's compose still pins VectorChord 0.4.3, so #980's trigger has not fired and immich-db stays. Refs #979 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The focused image updates are consistent, correctly pinned, and match the stated scope.
0 open findings
What changed in this PR
Updates both Immich services to v3.3.1 while preserving digest pinning and version alignment.
Changes:
- Bumps Immich server and machine-learning images to v3.3.1.
- Updates both immutable image digests.
| File | Description |
|---|---|
stacks/sensitive/compose.yaml |
Updates both Immich image pins. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Refs #979. The issue stays open after this merges. The weekly scan closes it on its own once the deployed digest scans clean, and v3.3.1 does not yet.
What
Both Immich images in
stacks/sensitive/compose.yamlgo to v3.3.1:immich-server→v3.3.1@sha256:db996e35…immich-machine-learning→v3.3.1@sha256:513c831c…Why
Scanned with the repo's pinned trivy using the CI flags (
--ignore-unfixed, HIGH/CRITICAL), against today's database:postgres:*-vectorchord0.4.3, so Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 67 high) #980's trigger has not fired andimmich-dbis unchanged.Checks
make lint: passed (4 skipped as unavailable, the usual ones)make check-docs: passedcheck_compose_health.py --probe stacks/sensitive/compose.yaml: passed.immich-healthcheckandpython3are present in the new images.After merge
Deploy the sensitive stack on trinity (
make up), then runmake check-container-health. Confirm Immich loads and its migrations finished in the server log.🤖 Generated with Claude Code