chore: backport Immich v3.2.3 and v3.2.4 onto main - #1151
Merged
Merged
Conversation
Backport of upstream immich-31644 (cherry-pick of immich-31642), shipped in Immich v3.2.3. (cherry picked from commit 91d34f9) Co-authored-by: Santo Shakil <santoshakil@users.noreply.github.com>
Backport of upstream immich-31854, shipped in Immich v3.2.4. Supersedes #1146: the new base image also ships a Node release past the 24.16-24.19 Blob stream leak (#1144). (cherry picked from commit 6786b82) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Daniel Dietzler <mail@ddietzler.dev>
With the two v3.2.3/v3.2.4 changes backported, main now contains everything in upstream v3.2.4. Neither release touches server/src/schema/, so the revert-to-immich script and the migration coverage are unchanged.
Deeds67
force-pushed
the
chore/backport-immich-3.2.4
branch
from
September 28, 2026 17:27
4a0dcc1 to
0eb38cd
Compare
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
1 participant
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.
Brings
mainup to upstream Immich v3.2.4 for a 5.7.1 patch release. Supersedes #1146.What v3.2.3 and v3.2.4 contain
Comparing
v3.2.2..v3.2.4on upstream'srelease/v3.2gives four commits. Two are version bumps. The other two are backported here:415b17f56f9, plus the newreset_sqlite_error_hintstring in the nine maintained locales202608300913→202609281550d2ea799f06eBoth cherry-picked onto
mainwithout conflicts. The third commit setsupstream.versionto3.2.4inbranding/config.json, updates the README, and updates the M8 preflight test.Base image and #1144
The new
base-server-prod:202609281550ships Node 24.21.0 (NODE_VERSIONin the image config). That is the version #1146 validated against theBlobstream leak. This PR includes that fix with a newer image, so #1146 can be closed once this merges.Checks done
server/src/schema/is identical between v3.2.2 and v3.2.4, so the revert-to-immich script and the migration coverage need no change.ghcr.io/immich-app/immich-server:v3.2.4is published (the revert-to-immich validation workflow boots it).202609281550.tools/upstream-preflighttests pass (292 passed, 1 skipped).Releasing
Server and mobile can ship separately. The mobile fix is client-only, with no API or schema change, so a 5.7.1 server works with 5.7.0 apps.
Rolling branch
rebase/upstream-rolling-v3.3.0already has the mobile fix and the older base-image bump. The newer bump arrives with the next batch. At cutover the replay will either drop these as already applied or give trivial conflicts, as with the v3.2.2 backport.