rmancinasandClaude Opus 5
db2bd545a1
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>
22 lines
509 B
JSON
22 lines
509 B
JSON
{
|
|
"name": "@jorgecuadros/database",
|
|
"version": "1.0.0",
|
|
"private": true,
|
|
"main": "generated/client/index.js",
|
|
"types": "generated/client/index.d.ts",
|
|
"scripts": {
|
|
"generate": "prisma generate",
|
|
"migrate:dev": "prisma migrate dev",
|
|
"migrate:deploy": "prisma migrate deploy",
|
|
"studio": "prisma studio",
|
|
"validate": "prisma validate",
|
|
"format": "prisma format"
|
|
},
|
|
"dependencies": {
|
|
"@prisma/client": "^5.20.0"
|
|
},
|
|
"devDependencies": {
|
|
"prisma": "^5.20.0"
|
|
}
|
|
}
|