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>
23 lines
637 B
JSON
23 lines
637 B
JSON
{
|
|
"name": "jorgecuadros-platform",
|
|
"version": "1.0.0",
|
|
"private": true,
|
|
"workspaces": [
|
|
"apps/*",
|
|
"packages/*"
|
|
],
|
|
"scripts": {
|
|
"dev:web": "npm run dev -w apps/web",
|
|
"dev:api": "npm run start:dev -w apps/api",
|
|
"build": "npm run build -ws --if-present",
|
|
"prisma:generate": "npm run generate -w packages/database",
|
|
"prisma:migrate": "npm run migrate:dev -w packages/database",
|
|
"prisma:deploy": "npm run migrate:deploy -w packages/database",
|
|
"prisma:studio": "npm run studio -w packages/database",
|
|
"version:set": "node scripts/set-version.mjs"
|
|
},
|
|
"engines": {
|
|
"node": ">=20"
|
|
}
|
|
}
|