Skip to content

Immich v3.0.0#15153

Merged
MickLesk merged 9 commits into
community-scripts:mainfrom
vhsdream:v3.0
Jul 2, 2026
Merged

Immich v3.0.0#15153
MickLesk merged 9 commits into
community-scripts:mainfrom
vhsdream:v3.0

Conversation

@vhsdream

@vhsdream vhsdream commented Jun 17, 2026

Copy link
Copy Markdown
Member

✍️ Description

Features

  • First, read the BREAKING CHANGES and migration guide straight from the Immich team. If you use any of the environment variables mentioned in the breaking changes then you must change them yourself, by editing /opt/immich/.env.
  • Mobile non-destructive editing
  • Workflows (in preview)
  • Background backup improvements on Android and iOS
  • A "Recently Added" page
  • Slideshow on mobile
  • HLS and Real-Time Video transcoding (in preview)
  • A new video player on web
  • "Open with Immich" in Android

Plus lots more - read about them all here

🔗 Related Issue

Fixes #15116

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to script metadata (PocketBase/website data).
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

@vhsdream vhsdream self-assigned this Jun 17, 2026
@github-actions github-actions Bot added breaking change A change that is not backward compatible feature refactor update script A change that updates a script core labels Jun 17, 2026
@vhsdream vhsdream force-pushed the v3.0 branch 3 times, most recently from bca91ae to 77a1968 Compare June 17, 2026 18:54
@CrazyWolf13

Copy link
Copy Markdown
Member

@vhsdream is this ready yet?

V3 will probably be released soon, as they just created the v3 tag: https://github.com/immich-app/immich/releases/tag/v3.0.0

also there seem to be conflicts.

@tremor021

Copy link
Copy Markdown
Member

Yea, lets hope they didn't break too much :)

@MickLesk

MickLesk commented Jul 1, 2026

Copy link
Copy Markdown
Member

If they do release it, I will be taking some time off of my own accord :D

@vhsdream

vhsdream commented Jul 1, 2026

Copy link
Copy Markdown
Member Author

I've been following the RCs, and yesterday I "updated" to the v3.0.0 tag with no issues. So far so good!

The only problem is that I'm still testing on Prod and during this I decided to upgrade VectorChord to 1.1.1 and it's not possible to downgrade 😦 so I hope eventually it's officially supported.

Let me take a look at the conflicts.

@vhsdream

vhsdream commented Jul 1, 2026

Copy link
Copy Markdown
Member Author

OK resolved and ready for more things to break!

@vhsdream vhsdream marked this pull request as ready for review July 2, 2026 19:14
@vhsdream vhsdream requested a review from a team as a code owner July 2, 2026 19:14
@vhsdream

vhsdream commented Jul 2, 2026

Copy link
Copy Markdown
Member Author

So it's out... and nothing really broke after I upgraded mine, although I've now noticed I have a bunch of files with a checksum mismatch in external libraries. Can still view them though.

@MickLesk

MickLesk commented Jul 2, 2026

Copy link
Copy Markdown
Member

I had some broken thumbnails (docker) and need to rerun the Jobs (fyi)

@MickLesk MickLesk merged commit a76225a into community-scripts:main Jul 2, 2026
3 checks passed
@N1V4K

N1V4K commented Jul 2, 2026

Copy link
Copy Markdown

Hello,

I got this error if i want to update

--- Last 20 lines of log ---
web build:   ✔ done
web build: Done
Packages are copied from the content-addressable store to the virtual store.
  Content-addressable store is at: /root/.local/share/pnpm/store/v11
  Virtual store is at:             ../app/cli/node_modules/.pnpm
? Verifying lockfile at ../app/cli/pnpm-lock.yaml against supply-chain policies (2665 entries)...
✓ Lockfile at ../app/cli/pnpm-lock.yaml passes supply-chain policies (2665 entries in 2.5s)
../app/cli                               | Progress: resolved 1, reused 0, downloaded 0, added 0
../app/cli                               |  +21 ++
../app/cli                               | Progress: resolved 21, reused 21, downloaded 0, added 21, done
mise ERROR Monorepo task paths (like `//path:task` or `:task`) require a monorepo root configuration.

To set up monorepo support, add this to your root mise.toml:
  monorepo_root = true

Then create task files in subdirectories that will be automatically discovered.
See https://mise.en.dev/tasks/task-configuration.html#monorepo-support for more information.
mise ERROR Version: 2026.7.0 linux-x64 (2026-07-02)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information
[2026-07-02 22:19:22] [ERROR] in line 208: exit code 1 (General error / Operation not permitted): while executing command mise //:plugins
  -----------------------------------

@niklasbraune

Copy link
Copy Markdown

Yeah, same problem for me, too.

web build: ✓ built in 14.56s
web build: Run npm run preview to preview your production build locally.
web build: > Using @sveltejs/adapter-static
web build: [PLUGIN_TIMINGS] Your build spent significant time in plugins. Here is a breakdown:
web build:   - vite-plugin-sveltekit-guard (77%)
web build:   - vite-plugin-sveltekit-virtual-modules (7%)
web build:   - imagetools (6%)
web build:   - vite-plugin-svelte:compile (4%)
web build: See https://rolldown.rs/options/checks#plugintimings for more details.
web build: 
web build:   Wrote site to "build"
web build:   ✔ done
web build: Done
Packages are copied from the content-addressable store to the virtual store.
  Content-addressable store is at: /root/.local/share/pnpm/store/v11
  Virtual store is at:             ../app/cli/node_modules/.pnpm
? Verifying lockfile at ../app/cli/pnpm-lock.yaml against supply-chain policies (2665 entries)...
✓ Lockfile at ../app/cli/pnpm-lock.yaml passes supply-chain policies (2665 entries in 3.5s)
../app/cli                               | Progress: resolved 1, reused 0, downloaded 0, added 0
../app/cli                               |  +21 ++
../app/cli                               | Progress: resolved 21, reused 21, downloaded 0, added 21, done
mise ERROR Monorepo task paths (like `//path:task` or `:task`) require a monorepo root configuration.

To set up monorepo support, add this to your root mise.toml:
  experimental_monorepo_root = true

Then create task files in subdirectories that will be automatically discovered.
See https://mise.jdx.dev/tasks/task-configuration.html#monorepo-support for more information.
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information
[2026-07-02 22:34:39] [ERROR] in line 208: exit code 1 (General error / Operation not permitted): while executing command mise //:plugins

@N1V4K

N1V4K commented Jul 2, 2026

Copy link
Copy Markdown

Also my complete Immich server is broken. Now restoring a backup

@henrikekblad

Copy link
Copy Markdown

Also got the monorepo error message when upgrading

@vhsdream

vhsdream commented Jul 2, 2026

Copy link
Copy Markdown
Member Author

Cool! What a fun disaster to figure out. Will dig into it later, have other things to handle right now.

@henrikekblad

Copy link
Copy Markdown

Cool! What a fun disaster to figure out. Will dig into it later, have other things to handle right now.

Good! Take your time. Proxmox snapshots is a great feature when this happens.

@MickLesk

MickLesk commented Jul 2, 2026

Copy link
Copy Markdown
Member

I’ve gone ahead and reverted the PR for now. Better to wait a day longer than to break several systems. I always think of the people who’ve never heard of snapshots. We’ll take another look tomorrow.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jul 10, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

breaking change A change that is not backward compatible core feature refactor update script A change that updates a script

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Immich v3 Preparation Addition to Immich script (when using mounts)

7 participants