Skip to content

Pictaria Server v1.1.0

Latest
Latest

Choose a tag to compare

View all tags
@dr-pictaria dr-pictaria released this 04 Sep 04:46
v1.1.0
e9e7222
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Pictaria Server v1.1.0 adds set-and-forget daily enrichment, broader local-model compatibility, a safer and faster Enrich workflow, and a more forgiving Curate review experience.

Upgrade

Follow the upgrade and rollback guide. Create and verify a complete backup before upgrading. If you use a custom BACKUP_DIR, complete its documented one-time adoption first. Then select the versioned image:

ghcr.io/pictaria-ai/pictaria-server:1.1.0

Verified multi-platform manifest:

ghcr.io/pictaria-ai/pictaria-server@sha256:a82cb5f318dc3bef32fd0457c8b23615edc3baee1909b663e483227c52b711c9

Platforms: linux/amd64 and linux/arm64.

Highlights

  • Daily Enrich can process a chosen budget of previously unenriched photos once per day, using the selected provider and sending successful results to Curate. Manual and queued work keeps priority, and automatic runs appear in Recent Runs.
  • A generic OpenAI-compatible provider connects Enrich, the Curate AI referee, and provider-selectable voice answers to llama.cpp and similar chat-completions servers using a configurable URL, model, and optional key.
  • Curate decisions now offer a five-second Undo (Z) action for individual photos and complete Stacks.
  • Recent Runs can re-run photos that still need work, load the complete retained history in pages, and show privacy-safe end-to-end throughput with provider, model, and an optional inference-host label.
  • Cancelling Enrich now aborts the active provider request immediately. Temporary provider overloads receive bounded, cancellation-aware retries, and shutdown records one honest terminal result.
  • Settings places Immich description-sync status beside its writeback control and clarifies the Pictaria Frame voice and TTS controls.

See the full v1.1.0 changelog.

Compatibility and rollback

  • A v1.0.1 installation migrates persisted Settings from v3 to v6 and the installation-state contract from v5 to v8. Intermediate contract versions were never publicly released.
  • Before migration, Pictaria creates and verifies a complete automatic pre-migration recovery snapshot. A rollback to v1.0.1 requires restoring that complete snapshot before starting the older server; do not point v1.0.1 at a v1.1.0-migrated data directory.
  • The Frame protocol, Node requirements, and Immich 2.0+ compatibility floor are unchanged.
  • Docker Compose installations should download the v1.1.0 Compose file and review the new OpenAI-compatible and Daily Enrich settings.

The exact release candidate completed a live v1.0.1 → v1.1.0 candidate → restored v1.0.1 → v1.1.0 candidate rehearsal against an existing persistent volume, adopted off-volume backup destination, and real Immich connection. Both pre-migration snapshots were verified; settings, application state, and Immich connectivity survived every transition.

For help, use Pictaria support. Report security issues privately as described in the security policy.

Source commit: e9e7222228156367d72dae8f7c61b7548e82c0c3

Assets 2
Loading