Skip to content

Pictaria Server v1.0.1

Latest
Latest

Choose a tag to compare

View all tags
@dr-pictaria dr-pictaria released this 02 Sep 22:55
· 3 commits to main since this release
v1.0.1
37dcff8
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.0.1 is a code-only patch release focused on Immich compatibility, enrichment reliability, and clearer behavior when upstream services return unexpected data.

Upgrade

Follow the upgrade and rollback guide. Create and verify a complete backup before upgrading, then select the immutable versioned image:

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

Verified multi-platform manifest:

ghcr.io/pictaria-ai/pictaria-server@sha256:63c84a1c89c70450fe882ff73806432dcb298570f91f4e57e03418dd96154a9c

Platforms: linux/amd64 and linux/arm64.

Highlights

  • Insights retains crowd photos containing more than 100 recognized people and safely handles oversized or malformed Immich EXIF metadata.
  • Enrich rejects prompt-label placeholder captions from small vision models.
  • LM Studio-compatible requests avoid socket hang up failures caused by stale reused connections and can consume valid structured output returned in reasoning_content.
  • OpenRouter requests adapt schemas for Gemini-compatible endpoints and report more useful, credential-redacted upstream errors.
  • Immich tag verification distinguishes unavailable tag data from failed repair attempts and provides targeted troubleshooting guidance.
  • Curate repairs contradictory eligibility, favorite, rejection, and review tags and adds a synchronized Load more control below the photo grid.
  • Docker Compose forwards all documented non-path enrichment, AI, voice, referee, and geocoding settings.

See the full v1.0.1 changelog.

Compatibility

  • Persisted-state contracts, the Frame protocol, Node requirements, and the Immich 2.0+ compatibility floor are unchanged from v1.0.0.
  • This release performs no startup data migration.
  • Docker Compose installations should review their .env before upgrading because documented settings omitted from earlier Compose files now take effect when configured.

The exact release candidate completed a live v1.0.0 → v1.0.1 → v1.0.0 → v1.0.1 rehearsal against a persistent data volume and a real Immich library. Backup, upgrade, rollback without restore, re-upgrade, retained settings and state, health checks, and browser checks all passed.

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

Source commit: 37dcff8ff23333f5018fd7ac77c396fd10a150ba

Assets 2
Loading