Pictaria Server v1.2.0 makes Enrich easier to configure, faster to run across an existing library, and clearer to inspect.
Before updating: create and verify a complete Pictaria backup. This release migrates stored data; rollback requires the pre-upgrade snapshot and its matching older build. This applies to Docker Compose and Unraid updates alike.
Highlights
- Reusable enrichment profiles: manage prompts and taxonomy in Settings, then choose one active profile on Enrich for sweeps, queued jobs, and Daily Enrich. Running work retains its saved settings.
- Performance you can inspect: a dedicated page shows run and photo timings, request median/average, timeouts and retries, and comparisons across providers/models/profiles. Open photos in Immich directly from run details.
- Faster library sweeps: a resumable local inventory avoids repeatedly walking already-enriched photos. New uploads are discovered even when their capture dates fall among older photos.
- AI tags arrive after enrichment: successful photos sync their AI tags to Immich whether or not they go to Curate. Pending or failed sync is visible and retryable without another AI call.
- Configurable history: retain 100–1,000 run summaries, with a separate 0–100-run log limit. Defaults remain 100 each.
- Simpler Enrich controls: provider and active profile share a card, profile editing stays in Settings, and routine already-enriched skips no longer clutter summaries or logs.
Upgrade
Follow the upgrade guide. Create and verify a complete backup before upgrading. Use the v1.2.0 Compose file and its matching versioned image:
ghcr.io/pictaria-ai/pictaria-server:1.2.0
Source commit: 629543820956f19ac2f05d46b3b13e90e4f98aaf.
Verified multi-platform image (linux/amd64 and linux/arm64):
ghcr.io/pictaria-ai/pictaria-server@sha256:d27ce98e2f055a927f7b37e7bac55f8a273cb0c122889e4be51cc6b5743a5154
The 1.2.0 and latest tags point to this same manifest. Both platform images identify the source commit above. Publication checks passed.
Behavior to know
- Confirm the initial My profile contains your existing customization. One active profile applies to all new enrichment runs; changing it does not alter running work.
- Only unenriched still skips all prior successes. Turning it off can reprocess historical results with unknown configuration inputs. Previously stuck photos can receive fresh attempts under the new configuration-aware failure accounting.
- Pictaria manages the complete ai/ tag namespace and may remove stale or manually added tags within it. Human frame/ decisions and unrelated tags are preserved. AI-tag searches/albums may now include photos before curation. Immich tag permissions are required, and older enriched photos are not automatically backfilled.
- Library sweeps send only their newly successful results to Curate. Explicit targeted selections can still send existing results.
- The first budgeted sweep builds an inventory. Periodic full metadata reconciliation on the first sweep after 24 hours is expected and does not mean every photo is being re-enriched.
Compatibility and rollback
v1.0.x installations can upgrade directly to v1.2.0 without first installing v1.1.0.
v1.1.0's Enrich schema 7/settings 6/persistent-state contract 8 upgrade to schema 12/settings 7/contract 15. Startup creates a complete pre-migration recovery snapshot. Rollback requires restoring that snapshot with its matching older build; never point an older server at upgraded state. Restoring Pictaria does not undo tags or captions already written to Immich.
Node requirements, the Frame protocol, and the Immich 2.0+ compatibility floor are unchanged. The container uses the existing pinned Node 22.23.2 Alpine base.
Validation includes 1,146 passing automated tests, reviewed upgrade/backup/restore checks, and user acceptance of the Enrich workflows. Independent actual-source rehearsals covered v1.0.1 and v1.1.0 upgrades and snapshot rollback. A user-reported live v1.1 → v1.2 rehearsal preserved settings and successful enrichment, followed by a successful return to v1.1. This is not a full Immich 3.2 compatibility certification or a load benchmark.
See the full changelog. For help, use Pictaria support; report security issues privately through the security policy.