Feature/gitea deployment workflow #1

Merged
Sluijsens merged 35 commits from feature/gitea-deployment-workflow into master 2026-07-29 16:50:44 +02:00
2 changed files with 12 additions and 0 deletions
Showing only changes of commit ff0fc66b10 - Show all commits
@@ -1429,3 +1429,13 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an
**Context**: OPERATIONS — Deployment Setup naming correction that required a small Construction-phase code change (deploy-scp.yaml) **Context**: OPERATIONS — Deployment Setup naming correction that required a small Construction-phase code change (deploy-scp.yaml)
--- ---
## Deployment Setup — First Real Pipeline Run Hit a Pre-Existing pnpm-workspace.yaml Bug
**Timestamp**: 2026-07-29T01:20:00Z
**User Input**: "Bij het draaien van de pipeline krijg ik bij de front-end prepare job het volgende: [pnpm install --frozen-lockfile fails with 'ERROR packages field missing or empty']"
**AI Response**: "Root cause: frontend/pnpm-workspace.yaml (committed since the original frontend setup, unrelated to this feature) has allowBuilds/confirmModulesPurge settings but never had a packages: field, which modern pnpm requires whenever a pnpm-workspace.yaml file exists at all, even for a single non-monorepo package. Added `packages: - '.'`. Verified locally: pnpm install --frozen-lockfile succeeds, lint clean."
**Context**: OPERATIONS — first real Gitea Actions pipeline run surfaced a pre-existing frontend config defect, fixed per the standing rule that small defects found in passing get fixed, not filed
---
+2
View File
@@ -1,3 +1,5 @@
packages:
- '.'
allowBuilds: allowBuilds:
'@tailwindcss/oxide': true '@tailwindcss/oxide': true
esbuild: true esbuild: true