rmancinasandClaude Opus 5 db2bd545a1 chore(release): v1.0.0 ...

Every manifest still read 0.1.0 while the deployed images were addressed by
the moving tag `latest`. That combination is what hid the stale-image bug:
a checkout could not be placed against a running container, and `latest`
silently kept serving two-commit-old web code through a green deploy.

Tagging v1.0.0 makes docker/metadata-action publish immutable `1.0.0` and
`1.0` image tags, so deploys can name a version instead of a moving target.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-07-30 16:21:35 -07:00

..

prisma

fix(docker): API image could never boot — missing workspace link and Prisma engine

2026-07-30 14:39:25 -07:00

package.json

chore(release): v1.0.0

2026-07-30 16:21:35 -07:00