Bump frontend to 0.1.2 to keep step with the backend rebuild
CI / test (push) Successful in 24s
CI / lint (push) Successful in 27s
CI / secrets-scan (push) Successful in 5s
CI / vuln-scan (push) Successful in 12s
CI / sast (push) Successful in 10s
CI / build-images (push) Successful in 1m47s
CI / image-scan (push) Successful in 45s
CI / push (push) Successful in 31s
CI / test (push) Successful in 24s
CI / lint (push) Successful in 27s
CI / secrets-scan (push) Successful in 5s
CI / vuln-scan (push) Successful in 12s
CI / sast (push) Successful in 10s
CI / build-images (push) Successful in 1m47s
CI / image-scan (push) Successful in 45s
CI / push (push) Successful in 31s
The push job's existence check runs per-service; leaving frontend at 0.1.1 (already in Harbor) would fail the gate even though only the backend image needed fixing. No frontend code changed — this is a forced bump to satisfy the per-service tag-overwrite guard. Harbor's layer dedup keeps the storage cost negligible. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "tehriehlbudget-frontend",
|
||||
"private": true,
|
||||
"version": "0.1.1",
|
||||
"version": "0.1.2",
|
||||
"type": "module",
|
||||
"scripts": {
|
||||
"dev": "vite",
|
||||
|
||||
Reference in New Issue
Block a user