Skip to content

feat(container): update image ghcr.io/immich-app/immich-server to v1.134.0 #303

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(container): update image ghcr.io/immich-app/immich-server to v1.134.0 #303

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 2, 2024 •
edited
Loading

This PR contains the following updates:

Package Update Change
ghcr.io/immich-app/immich-server minor v1.129.0 -> v1.134.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

immich-app/immich (ghcr.io/immich-app/immich-server)

v1.134.0

Compare Source

v1.134.0

Welcome to release v1.134.0 of Immich. This release focuses on bug fixes and enhancements from the previous release. Please find some of the highlights below:

  • Adds a new API endpoint to check the application version status
  • Adds a mechanism to handle startup reindexing after a failed model change
  • Improves pinch-to-zoom action on the mobile app
  • Replaces the administration user edit button with the action button to go straight to the user's detail page
  • Fixes a bug where generated memories include locked assets
  • Fixes a bug where the search filter panel anchors to the top of the page instead of the viewport
  • Fixes a bug where ctrl/cmd + click doesn't open the photo on a new page
  • Fixes various minor issues related to styling and z-index

Support Immich

What's Changed

🌟 Enhancements
🐛 Bug fixes
🌐 Translations

New Contributors

Full Changelog: immich-app/immich@v1.133.1...v1.134.0

v1.133.1

Compare Source

v1.133.1

Highlights

  • Lower disk usage during VectorChord migration
  • Adds move to locked album button to more views on the web
  • Fixes a bug where the missing button for the duplicate detection job is not working
  • Fixes a bug where a hard link does not navigate to the asset location on the timeline
  • Fixes a bug where styling information is missing in some cases
  • Fixes a bug where locked assets show up in local album view if it is presented on the phone
  • Fixes some translation issues

What's Changed

🌟 Enhancements
🐛 Bug fixes
📚 Documentation
🌐 Translations

New Contributors

Full Changelog: https://github.com/immich-app/immich/compare/v1.133.0...

v1.133.0

Compare Source

v1.133.0 - The Hot Summer Release

[!CAUTION]

BREAKING CHANGES

  1. Mobile app version

    Please make sure to have the mobile app and the server on the same version for this release. Older versions of the mobile app will not work correctly with version v1.133.0 of the server. At the time of this release, the updated version of the mobile app should be available on the app stores.

  2. Upgrading the server from a very old release

    As of 1.133.0, Immich only supports upgrading directly from 1.107.2 or later. If you’re trying to upgrade a version of Immich below this, please upgrade to 1.107.2 first and ensure Immich starts up successfully before continuing to the latest release.

  3. New database vector extension

    We are migrating off the deprecated pgvecto.rs database extension to its successor VectorChord, which comes with performance improvements in almost all aspects. This change is a major milestone we want to perform prior to the stable release.

Before making any other changes, please back up your database. While every effort has been made to make this migration as smooth as possible, there’s always a chance that something can go wrong.

After making a backup, please modify your docker-compose.yml file with the following information.

  [...] 

  database:
    container_name: immich_postgres
-   image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@​sha256:739cdd626151ff1f796dc95a6591b55a714f341c737e27f045019ceabf8e8c52
+   image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
+     # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
+     # DB_STORAGE_TYPE: 'HDD'
    volumes:

### Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
-   healthcheck:
-     test: >-
-       pg_isready --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" || exit 1;
-       Chksum="$$(psql --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" --tuples-only --no-align
-       --command='SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database')";
-       echo "checksum failure count is $$Chksum";
-       [ "$$Chksum" = '0' ] || exit 1
-     interval: 5m
-     start_interval: 30s
-     start_period: 5m
-   command: >-
-     postgres
-     -c shared_preload_libraries=vectors.so
-     -c 'search_path="$$user", public, vectors'
-     -c logging_collector=on
-     -c max_wal_size=2GB
-     -c shared_buffers=512MB
-     -c wal_compression=on
    restart: always

    [...]

If you deviated from the defaults of pg14 or pgvectors0.2.0, you must adjust the pg major version and pgvecto.rs version. If you are still using the default docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0 image, you can just follow the changes above. For example, if the previous image is docker.io/tensorchord/pgvecto-rs:pg16-v0.3.0, the new image should be ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvectors0.3.0 instead of the image specified in the diff.

After making these changes, you can start Immich as normal. Immich will make some changes to the DB during startup, which can take seconds to minutes to finish, depending on hardware and library size. In particular, it’s normal for the server logs to be seemingly stuck at Reindexing clip_index and Reindexing face_indexfor some time if you have over 100k assets in Immich and/or Immich is on a relatively weak server. If you see these logs and there are no errors, just give it time.

[!IMPORTANT]
Note: after switching to VectorChord, you should not downgrade Immich below 1.133.0.

Please don’t hesitate to contact us here on GitHub or Discord if you encounter migration issues.

VectorChord FAQ

I have a separate PostgreSQL instance shared with multiple services. How can I switch to VectorChord?

Please see https://immich.app/docs/administration/postgres-standalone#migrating-to-vectorchord for migration instructions. The migration path will be different depending on whether you’re currently using pgvecto.rs or pgvector, as well as whether Immich has superuser DB permissions.

What will happen if I upgrade Immich to 1.133.0 without changing the DB image?

Immich will auto-detect the vector extension available in the DB and continue to work without manual intervention. However, we will drop support for pgvecto.rs in a later release, so please switch at your convenience.

I’m using a different deployment method than Docker Compose. How should I migrate?

If you’re using Immich through turnkey deployment methods such as TrueNAS apps, the respective maintainers will either perform the migration transparently or inform you of what to do if not.

Why are so many lines removed from the docker-compose.yml file? Does this mean the health check is removed?

These lines are now incorporated into the image itself along with some additional tuning.

What does this change mean for my existing DB backups?

The new DB image includes pgvector and pgvecto.rs in addition to VectorChord, so you can use this image to restore from existing backups that used either of these extensions. However, backups made after switching to VectorChord require an image containing VectorChord to restore successfully.

Do I still need pgvecto.rs installed after migrating to VectorChord?

pgvecto.rs only needs to be available during the migration, or if you need to restore from a backup that used pgvecto.rs. For a leaner DB and a smaller image, you can optionally switch to an image variant that doesn’t have pgvecto.rs installed after you’ve performed the migration and started Immich: ghcr.io/immich-app/postgres:14-vectorchord0.3.0, changing the PostgreSQL version as appropriate.

Why does it matter whether my database is on an SSD or an HDD?

These storage mediums have different performance characteristics. As a result, the optimal settings for an SSD are not the same as those for an HDD. Either configuration is compatible with SSD and HDD, but using the right configuration will make Immich snappier. As a general tip, we recommend users store the database on an SSD whenever possible.

Can I use the new database image as a general PostgreSQL image outside of Immich?

It’s a standard PostgreSQL container image that additionally contains the VectorChord, pgvector, and (optionally) pgvecto.rs extensions. If you were using the previous pgvecto.rs image for other purposes, you can similarly do so with this image.

If pgvecto.rs and pgvector still work, why should I switch to VectorChord?

VectorChord is faster, more stable, uses less RAM, and (with the settings Immich uses) offers higher-quality results than pgvector and pgvecto.rs. This translates to better search and facial recognition experiences. In addition, pgvecto.rs support will be dropped in the future, so changing it sooner will avoid disruption.

Highlights

Welcome to the release v1.133.0 of Immich, which is the hottest release yet for this summer, with more than 200 commits since the last version. This version brings you a new database extension, an even more optimized and faster timeline, more unified components on the web, some cool new features that have been requested for a long time, and many bug fixes and improvements. Let’s dive in!

  • VectorChord database extension
  • In-app notification
  • Show map in albums view (web only)
  • Locked folder
  • Google Cast Support (web only)
  • User detail page
  • RTL text support on the web
  • Performance improvement in web timeline
  • Notable fix: thumbnail caching issue on the mobile app
  • Notable fix: For users who use OAuth, you can now configure TOKEN_ENDPOINT_AUTH_METHOD to either client_sect_post or client_secret_basic after entering the CLIENT_SECRET
  • Sneak peek
In-app notification

Introducing an in-app, or internal, notification system. Previously, there was no way to notify you on the client if a database backup failed. Now, the failed backup will show up under a new notification section on the web. This mechanism paves the way for other helpful notifications, such as when a new album is shared with you or when new assets are added to a shared album, directly in the app.

Show map in albums view

On the web, you can now click this button to see the map view that shows the location of all the photos and videos in an album.

Locked folder

Have you ever taken embarrassing selfies that you don’t want anyone to see, and worry that you could accidentally reveal them while showcasing your superb Immich library? Locked folder view got you covered, with a personal PIN code, and an option to use biometric verification on the mobile app. You can access the page from the sidebar on the web or in the Library page on the app

locked-web-demo-cut.mp4

)

You can select any assets and add them to the locked folder. They will only be shown in the locked folder view.

Google Cast Support

We now have casting support! Immich now supports casting to Google Cast enabled devices like the Google Chromecast. This feature is currently only available on the web, with mobile app support coming in the near future. You can use images, videos and slideshows with casting.

image image

[!NOTE]

Your Immich instance must be accessed through a public HTTPS endpoint in order for the casting device to successfully load media. Accessing the instance and casting from a private HTTPS endpoint (or an HTTP endpoint) will result in the cast receiver failing to load any media.

User detail page

From the user management page of the admin view, you can now get a more in-depth view of individual users for their information, usage statistics, and which features they have enabled, etc, by clicking on the email from the user’s table

image image

RTL text support on the web

The web styling has been changed to accommodate RTL languages

image
Performance improvement in web timeline

Last time, we discussed thinking that the timeline performance has reached its prime and that adding more gains would be difficult. In this release, we managed to squeeze that gain like a ripe orange.

The timeline will automatically cancel the requests to the server when you scroll very fast, displaying the thumbnails instantaneously when the scrolling stops. Previously, the web needed to finish the requests for the thumbnails being scrolled by, even if they are not displayed on the viewport. This change significantly reduces the load time.

An additional optimization has been made to reduce the data packet for each thumbnail to about 30% of its original size. This optimization contributes to a greater loading speed on the timeline.

We hope you enjoy these impressive improvements.

Sneak Peak

Besides the cool features and enhancements that made their way into the application, along with many bug fixes, our highest priority at the moment is moving toward the stable release. A big chunk of time and dedication from the team is now spent on improving the mobile app synchronization system, basically rewriting the flow and designing the data model from the ground up. At the same time, we’re working to properly allocate CPU-intensive tasks to background threads to avoid app stuttering and jerkiness when the data sync between the server and the mobile app happens.

Below is the chart result comparing the local album sync between the current version and the reworked version.

Current version
image

Improved version
image

We are working hard to get it into the application in the coming months and are very excited about this new improvement.

Cheers!

The Immich Team

Support Immich

If you find the project helpful, you can support Immich by purchasing a product key at https://buy.immich.app or purchase our merchandise at https://immich.store

What's Changed

🚨 Breaking Changes
🚀 Features
🌟 Enhancements
🐛 Bug fixes
📚 Documentation
🌐 Translations

New Contributors

Full Changelog: https://github.com/immich-app/immich/compare/v1.132.3...

v1.132.3

Compare Source

v1.132.3

Bug fixes

  • Opt-in delete sync is now available on Android!
    We found an alternative method to achieve this. The feature is now available on Android. We are excited to hear about your experience with the feature. Please read this note about the feature
  • Fixes an issue where the mobile app cannot log in with an instance using Authelia for OAuth.

[!IMPORTANT]
Please update your Authelia config with the following property

token_endpoint_auth_method: "client_secret_post"
  • Fixes an issue where navigating to the Library page could trigger a location permission request
  • Fixes an issue where the mobile app might rehash some of the assets

What's Changed

🐛 Bug fixes
📚 Documentation

New Contributors

Full Changelog: immich-app/immich@v1.132.1...v1.132.3

v1.132.1

Compare Source

v1.132.1

Hotfixes

  • Reverting the opt-in delete synchronization in this release 😢. There is an issue with getting the Google PlayStore to approve the app with the new permission needed for this feature. We are exploring alternative routes to preserve this feature and will push out another update as soon as possible
  • Fixes an issue where the server does not start on ARM devices

What's Changed

🐛 Bug fixes

Full Changelog: immich-app/immich@v1.132.0...v1.132.1

v1.132.0

Compare Source

v1.132.0

Highlights

[!NOTE]
We are now using Valkey's image for the Redis service in the default docker-compose.yml template. This is not a required change. If you wish to use it, you can download the docker-compose.yml file at the bottom of the release notes and replace the redis image with the new one.

Welcome to version v1.132.0 of Immich.

This release marks an exciting milestone, inching one step closer to the stable release. The server no longer relies on TypeORM (database object-relational mapping); from this point forward, we utilize our own schema and migration management tool, integrated with Kysely. Related, the mobile app will also begin to use a new database, SQLite. Over the next few releases, we plan to roll out a new, efficient sync implementation using SQLite, which should improve startup time and reduce jankiness, especially when working with large media collections.

In addition to the two milestones mentioned above, this release also features new enhancements, bug fixes, and other notable additions. Please see the highlights below.

  • Opt-in web-mobile delete action synchronization on Android
  • Improve web responsive design on mobile devices
  • Migrate mobile app translations to Weblate
  • Improve mobile app map performance
Opt-in web-mobile delete synchronization (Android only)

This update includes a new, optional feature currently in an experimental phase. It aims to synchronize deletion actions between the Immich web interface and your connected Android device.

If you choose to enable this feature (Settings > Advanced > Sync remote deletion), trashing, deleting, or restoring a photo or video through the Immich web interface will result in the corresponding action being taken on the file on your Android phone. This functionality is intended to prevent the need to perform the same trash action separately on both Immich and your phone.

When this feature is active, the sequence of events is as follows:

  1. Your photos get backed up from your phone to Immich.
  2. Later, you use the Immich website to trash some of those photos.
  3. The next time you open the Immich app on your phone, the app will find those photos you trashed on the website and move them to your phone's trash folder for you.
  4. If you choose to restore the asset from Immich’s trash, it will also be moved out of your phone’s trash folder.

Note: The location of the phone's trash folder varies by device. For example, Samsung devices often use the Gallery app's trash, while Google Pixel devices may use the Files app's trash.)

Improve web responsive design on mobile devices.

This release makes significant improvements to the browsing experience of the web app on mobile devices. The sidebar is now collapsible, leaving more space to view the timeline. We’ve also changed the size of the images in the timeline on mobile, with the hope of making more images visible at once.

Just as we thought we had squeezed every ounce of performance out of the timeline scrolling, a wizard in the contributor team pushed it even further. The need for speed is real! We hope you enjoy it.
Mobile app translations have been migrated to Weblate.

The i18n on the mobile app, previously managed with Localizely, has now been migrated to Weblate. Anyone can help with translation without needing to obtain an invitation from us.

Along with those changes, we have made many more improvements to the quality of the server, web, and mobile app. We hope you enjoy those as well.

Support Immich

If you find the project helpful, you can support Immich by purchasing a product key at https://buy.immich.app or purchase our merchandise at https://immich.store

What's Changed

🚨 Breaking Changes
🔒 Security
🚀 Features
🌟 Enhancements
🐛 Bug fixes

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions GitHub Actions
Copy link

github-actions bot commented Nov 2, 2024 •
edited
Loading 

--- kubernetes/apps/media/immich/app Kustomization: flux-system/cluster-apps-immich HelmRelease: immich/immich-server

+++ kubernetes/apps/media/immich/app Kustomization: flux-system/cluster-apps-immich HelmRelease: immich/immich-server

@@ -42,13 +42,13 @@

             - configMapRef:
                 name: immich-configmap
             - secretRef:
                 name: immich-secret
             image:
               repository: ghcr.io/immich-app/immich-server
-              tag: v1.129.0
+              tag: v1.134.0
         pod:
           topologySpreadConstraints:
           - labelSelector:
               matchLabels:
                 app.kubernetes.io/name: immich-server
             maxSkew: 1

@github-actions GitHub Actions
Copy link

github-actions bot commented Nov 2, 2024 •
edited
Loading 

--- HelmRelease: immich/immich-server Deployment: immich/immich-server

+++ HelmRelease: immich/immich-server Deployment: immich/immich-server

@@ -45,13 +45,13 @@

       containers:
       - envFrom:
         - configMapRef:
             name: immich-configmap
         - secretRef:
             name: immich-secret
-        image: ghcr.io/immich-app/immich-server:v1.129.0
+        image: ghcr.io/immich-app/immich-server:v1.134.0
         livenessProbe:
           failureThreshold: 3
           initialDelaySeconds: 0
           periodSeconds: 10
           tcpSocket:
             port: 2283

@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.119.1 feat(container): update image ghcr.io/immich-app/immich-server to v1.120.0 Nov 6, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 3d694a0 to e5fe820 Compare November 6, 2024 17:08
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.120.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.120.1 Nov 7, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch 2 times, most recently from 2f8b879 to b73df81 Compare November 12, 2024 20:01
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.120.1 feat(container): update image ghcr.io/immich-app/immich-server to v1.120.2 Nov 12, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from b73df81 to b383168 Compare November 20, 2024 17:23
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.120.2 feat(container): update image ghcr.io/immich-app/immich-server to v1.121.0 Nov 20, 2024
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.121.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.121.0 - autoclosed Dec 2, 2024
@renovate renovate bot closed this Dec 2, 2024
@renovate renovate bot deleted the renovate/ghcr.io-immich-app-immich-server-1.x branch December 2, 2024 12:06
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.121.0 - autoclosed feat(container): update image ghcr.io/immich-app/immich-server to v1.121.0 Dec 7, 2024
@renovate renovate bot reopened this Dec 7, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 243ef3c to b383168 Compare December 7, 2024 00:33
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.121.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.122.1 Dec 7, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch 2 times, most recently from 367e281 to 1f6a869 Compare December 9, 2024 00:34
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.122.1 feat(container): update image ghcr.io/immich-app/immich-server to v1.122.2 Dec 9, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 1f6a869 to 3f59ce1 Compare December 13, 2024 16:45
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.122.2 feat(container): update image ghcr.io/immich-app/immich-server to v1.122.3 Dec 13, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 3f59ce1 to 2c2db41 Compare December 17, 2024 17:34
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.122.3 feat(container): update image ghcr.io/immich-app/immich-server to v1.123.0 Dec 17, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 2c2db41 to 72ebbdf Compare January 7, 2025 20:27
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.123.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.124.0 Jan 7, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 72ebbdf to 62f26d9 Compare January 8, 2025 21:22
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.124.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.124.1 Jan 8, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 49a45a6 to 7efec10 Compare March 29, 2025 02:42
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.129.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.130.3 Mar 29, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch 2 times, most recently from 8ff737b to 6789712 Compare March 31, 2025 19:55
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.130.3 feat(container): update image ghcr.io/immich-app/immich-server to v1.131.0 Mar 31, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 6789712 to 9de1b51 Compare March 31, 2025 23:55
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.131.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.131.1 Mar 31, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 9de1b51 to a5def8a Compare April 1, 2025 17:01
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.131.1 feat(container): update image ghcr.io/immich-app/immich-server to v1.131.2 Apr 1, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from a5def8a to f8c74b9 Compare April 2, 2025 01:35
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.131.2 feat(container): update image ghcr.io/immich-app/immich-server to v1.131.3 Apr 2, 2025
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.131.3 feat(container): update image ghcr.io/immich-app/immich-server to v1.131.3 - autoclosed Apr 14, 2025
@renovate renovate bot closed this Apr 14, 2025
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.131.3 - autoclosed feat(container): update image ghcr.io/immich-app/immich-server to v1.131.3 Apr 19, 2025
@renovate renovate bot reopened this Apr 19, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch 2 times, most recently from f8c74b9 to fd4f27e Compare April 19, 2025 06:14
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.131.3 feat(container): update image ghcr.io/immich-app/immich-server to v1.132.0 Apr 23, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch 2 times, most recently from 45d2d91 to 271b9be Compare April 23, 2025 22:55
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.132.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.132.1 Apr 23, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 271b9be to 79e3592 Compare April 28, 2025 20:44
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.132.1 feat(container): update image ghcr.io/immich-app/immich-server to v1.132.3 Apr 28, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 79e3592 to 7090eb2 Compare May 22, 2025 03:14
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.132.3 feat(container): update image ghcr.io/immich-app/immich-server to v1.133.0 May 22, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 7090eb2 to 34b7ded Compare May 23, 2025 19:04
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.133.0 feat(container): update image ghcr.io/immich-app/immich-server to v1.133.1 May 23, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-immich-app-immich-server-1.x branch from 34b7ded to cfa066a Compare May 27, 2025 19:36
@renovate renovate bot changed the title feat(container): update image ghcr.io/immich-app/immich-server to v1.133.1 feat(container): update image ghcr.io/immich-app/immich-server to v1.134.0 May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate/container type/minor
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants