Update ghcr.io/immichframe/immichframe Docker tag to v1.0.37.0 - #94
Open
renovate[bot] wants to merge 1 commit into
Open
Update ghcr.io/immichframe/immichframe Docker tag to v1.0.37.0#94renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
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.
This PR contains the following updates:
v1.0.34.0→v1.0.37.0Release Notes
immichFrame/ImmichFrame (ghcr.io/immichframe/immichframe)
v1.0.37.0Compare Source
📦 ImmichFrame Release v1.0.37.0 – July 17, 2026
This release rolls back the memories timezone workaround now that Immich fixes memory date handling upstream.
What's Changed
⚡ Fixes
🐛 Revert memories timezone fix
PR #678 by @JW-CH
ImmichFrame previously appended a timezone offset to the Immich memories
forquery parameter (#660) to work around inconsistent date handling. Immich has since fixed memory search date validation upstream(immich-app/immich#29907), so that workaround is no longer needed and now conflicts with the server-side behavior. This release reverts it, restoring plain calendar-date filtering so your memories show up correctly again. The bundled Immich
OpenAPI spec was refreshed as part of the revert.
Full Changelog: immichFrame/ImmichFrame@v1.0.36.0...v1.0.37.0
v1.0.36.0Compare Source
📦 ImmichFrame Release v1.0.36.0 – July 14, 2026
This release adds a startup guard that fails fast when ImmichFrame is pointed at an incompatible Immich server, logs each server's version, and cleans up how settings are handled internally.
What's Changed
✨ New Features
🚦 Startup version check enforces Immich v3
PR #676 by @JW-CH
ImmichFrame already targets the Immich v3 API — this release now enforces it at startup. On boot, it checks the version of every configured Immich server and refuses to start if any server is older than v3, is unreachable, or its version can't be determined. Previously, an incompatible (older) server would let ImmichFrame start but then fail later with a cryptic
deserialization error — for example, Immich changed an asset's
durationfrom a string like"0:00:00.00000"to integer milliseconds, which broke image loading. Now you get a clear critical log message naming the affected server, and the container stops instead of silently misbehaving.What you need to do: Make sure your Immich server(s) are on v3.0 or newer. If ImmichFrame won't start, check the logs for the offending server.
The bundled Immich OpenAPI spec was also bumped to 3.0.2 as part of this change.
📋 Immich server version logging
PR #673 by @JW-CH
ImmichFrame now logs the version of each configured Immich server at startup, so you can confirm compatibility at a glance. Previous startup log noise was trimmed at the same time, making the logs easier to read.
🔨 Maintenance
🔧 Simplified settings handling
PR #667 by @JW-CH
Settings are now split into dedicated client and server interfaces. As a result, the
/api/Configendpoint is structurally limited to client-safe values only — server-only secrets such as API keys, the webhook URL, the authentication secret, and web-calendar URLs can no longer reach the client. This change also makes the per-account asset tracker (BloomFilter) thread-safe and reworks how the account-selection strategy is constructed for more reliable multi-account setups.Full Changelog: immichFrame/ImmichFrame@v1.0.35.0...v1.0.36.0
v1.0.35.0Compare Source
📦 ImmichFrame Release v1.0.35.0 – July 8, 2026
This release fixes memories failing to load against newer Immich servers, along with a stale QR code/link bug in the info overlay.
What's Changed
⚡ Fixes
🐛 Fixed memories not loading on newer Immich servers
PR #660 by @JW-CH
The "on this day" memories row could fail to load entirely against newer Immich servers, which now strictly require a timezone offset on the date sent to the memories endpoint. ImmichFrame was dropping that offset before sending the request, causing Immich to reject it. The request now correctly includes your local timezone offset, so memories load reliably again.
🐛 Fixed stale QR code and "Open in Immich" link during slideshow
PR #666 by @JoeRu
The QR code and "Open in Immich" link in the info overlay could get stuck pointing at the first photo shown, even after the slideshow moved on to new images. Opening the info overlay now always shows the QR code and link for the photo currently on screen.
New Contributors
Full Changelog: immichFrame/ImmichFrame@v1.0.34.0...v1.0.35.0
Configuration
📅 Schedule: (UTC)
🚦 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.