github pictaria-ai/pictaria-server v1.2.3
Pictaria Server v1.2.3

58 minutes ago

Pictaria Server v1.2.3 updates the container's Node.js runtime from 22.23.2 to 22.23.5 to pick up Node's October and November 2026 security fixes. Pictaria Server's own code is unchanged from v1.2.2.

Security

  • Node.js 22.23.5: The container image now runs Node.js 22.23.5. It includes the October 21 and November 11, 2026 Node.js security releases (22.23.4 and 22.23.5). The image stays on Node 22 and the same Alpine 3.24 base, pinned to the official multi-platform image digest. We have not tested which of the fixed flaws can be reached through Pictaria Server; this release takes the patched runtime regardless.
  • Bare-Node installations should run Node.js 22.23.5 or a later 22.x release. Node 22 reaches end-of-life on April 30, 2027.

Upgrade

Back up Pictaria, then follow the v1.2.3 upgrade guide. Use the tagged Compose file and matching image:

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

From v1.2.2, no persisted-state migration occurs: contract 15, Enrich schema 12 and settings version 7 are unchanged. No new setting or data-folder change is needed. If no other migration occurred, you can stop the server and return to v1.2.2 without restoring data; that release runs Node 22.23.2, without these fixes. v1.2.0 and v1.2.1 installations share the same contracts and can also update directly.

From v1.0.x or v1.1.0, direct upgrade is supported, but the v1.2 data migrations still run. Keep the complete pre-migration snapshot and the matching older build for rollback.

After updating, confirm Settings → Server shows v1.2.3, then restart the container and confirm it stays healthy.

The engines range, the Pictaria Frame protocol and the Immich 2.0+ compatibility floor are unchanged. No Immich or Pictaria Frame upgrade is required.

Validation

The full suite on Node 22.23.5 as a non-root user completed with 1,166 tests: 1,161 passed, zero failed and five Chrome-only tests skipped. PR CI passed Server tests, Upgrade compatibility, Container build and boot smoke, and DCO sign-off. Publication hygiene and DCO checks passed. Both container platforms built locally. On native arm64 and on emulated amd64, a fresh volume upgraded from the published 1.2.2 image to 1.2.3 and stayed healthy through two restarts as a non-root user. Returning to 1.2.2 on the same volume was also healthy. Databases written under Node 22.23.5's SQLite 3.54.1 passed integrity checks under v1.2.2's SQLite 3.51.3.

See the full changelog.

Published image

Source commit: 84a64cf1ebab8e6cd672c579678295751bfccb6e.

Verified multi-platform image (linux/amd64 and linux/arm64):

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

The 1.2.3 and latest tags resolve to this manifest, which contains both platforms. The published native arm64 container reports version 1.2.3 and Node v22.23.5, runs as non-root UID 1000, and stays healthy after a restart. The published amd64 image also reports 1.2.3 and Node v22.23.5 as UID 1000. Both platforms' source-revision labels match the commit above. The 1.2.2 tag keeps its original manifest digest, sha256:3f8889da6218ede13d74b330e851ef9ff6a94ee0df9a2b9f4f727bfba5db1e0e, and 1.2.1 keeps sha256:ab24656436246500d457c7155c3b1a6b2001b9cfbaa69ef0e3ef79aea83f8729. Publication checks passed.

Don't miss a new pictaria-server release

NewReleases is sending notifications on new releases.