Skip to content

chore(sensitive): Immich v3.2.4 -> v3.3.1, ahead of Sunday's Dependabot (#979) - #1129

Merged
Gerrrt merged 1 commit into
mainfrom
gerrrt/immich-v3.3.1-979
Oct 10, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
gerrrt/immich-v3.3.1-979

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Oct 10, 2026

Copy link
Copy Markdown
Owner

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.yaml go 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:

Image v3.2.4 (pinned) v3.3.1
immich-server 4 critical / 48 high 4 critical / 34 high
immich-machine-learning 4 critical / 26 high 4 critical / 27 high
  • Server: Debian's gzip, sqlite and openssl are fixed, and so are npm's compression, multer and sharp. The remaining findings (proxy-addr, tar, brace-expansion, fast-uri, undici, ws, socket.io-parser, grpc-js, js-yaml, ip-address, handlebars) are transitive npm dependencies inside upstream's build. Only an Immich release can fix them.
  • Machine learning moves only because server and ML must stay on the same version. It is not cleaner: v3.3.1 rebased onto a newer Debian. Its triage is on Fixable CVEs in ghcr.io/immich-app/immich-machine-learning (2 critical, 18 high) #978, so this PR does not reference that issue.
  • No breaking changes are listed in the v3.3.0 or v3.3.1 notes. Upstream's compose still pins postgres:*-vectorchord0.4.3, so Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 67 high) #980's trigger has not fired and immich-db is unchanged.

Checks

  • make lint: passed (4 skipped as unavailable, the usual ones)
  • make check-docs: passed
  • check_compose_health.py --probe stacks/sensitive/compose.yaml: passed. immich-healthcheck and python3 are present in the new images.

After merge

Deploy the sensitive stack on trinity (make up), then run make check-container-health. Confirm Immich loads and its migrations finished in the server log.

🤖 Generated with Claude Code

…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>
Copilot AI balanced review requested due to automatic review settings October 10, 2026 14:18
@Gerrrt Gerrrt added security A credential, an exposure, or a control that is weaker than recorded sensitive stacks/sensitive on trinity (VLAN 99) labels Oct 10, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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.

@Gerrrt
Gerrrt enabled auto-merge (squash) October 10, 2026 14:21
@Gerrrt
Gerrrt merged commit 1c628f3 into main Oct 10, 2026
9 checks passed
@Gerrrt
Gerrrt deleted the gerrrt/immich-v3.3.1-979 branch October 10, 2026 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security A credential, an exposure, or a control that is weaker than recorded sensitive stacks/sensitive on trinity (VLAN 99)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants