All versions since [0.3.11]

[0.3.11]

Aug 28, 2026

README section documenting the containerd image store and a troubleshooting checklist for ImagePullBackOff after a deploy.

The registry auth payload sent during push now includes serveraddress, so Docker Desktop routes credentials to the pinexq registry on every version.
Update build backend uv_build to >=0.12.6,<0.13.0.

deploy now aborts when the image push reports an error instead of reporting success. Previously a failed or partial push was swallowed and an unpullable code hash was registered, causing rare ImagePullBackOff failures in Kubernetes.
The registered code hash is now the digest reported for the push and is verified to exist in the registry before it is assigned, instead of a locally derived digest (RepoDigests/image ID) that could name a manifest the registry does not hold.

Update dependency copier to 9.17.2, fixing CVE-2026-53951 (trust-prefix bypass via path traversal that could run template tasks unprompted).
Update dev dependency pytest to 9.1.1, fixing CVE-2025-71176 (unsafe /tmp directory handling).

Sep 3, 2026

Read-only list and show commands for six JMA Resources: job, workdata (alias wd), processing-step (alias ps), template, trigger, and folder. Each supports table, JSON, CSV, and quiet (-q) output, --wide, pagination (--limit/--offset/--all), sorting, and per-Resource filters; show accepts a UUID or URL for every noun, name@version for ProcessingSteps, and a /path for Folders. These commands resolve their connection leniently (flag → env → pinexq.toml) and run from any directory.
--help for every read command groups options into Connection / Output / Pagination / Filters panels; the enum filters (--state, --kind, --deployment-state) list their valid values and offer shell tab-completion.
Shell completion is enabled (pinexq --install-completion / --show-completion).
README “Reading Resources” section documenting the new commands.