SLP_Software/slp-modular-cms
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

Adds the missing packages field to pnpm-workspace.yaml
Continuous Integration / config (pull_request) Successful in 10s
Details
Continuous Integration / backend-build (pull_request) Successful in 4m1s
Details
Continuous Integration / vulnerability-scan (pull_request) Successful in 3m38s
Details
Continuous Integration / frontend-prepare (pull_request) Successful in 1m22s
Details
Continuous Integration / backend-test (pull_request) Successful in 4m39s
Details
Continuous Integration / frontend-build (pull_request) Successful in 2m6s
Details
Continuous Integration / frontend-test (pull_request) Failing after 6m22s
Details
Continuous Integration / frontend-lint (pull_request) Successful in 1m58s
Details
Continuous Integration / publish-test (pull_request) Skipped
Details
Continuous Integration / publish-production (pull_request) Skipped
Details
Continuous Integration / deploy-test (pull_request) Skipped
Details
Continuous Integration / deploy-production (pull_request) Skipped
Details

Browse Source 
Pre-existing file from the original frontend setup - had allowBuilds
and confirmModulesPurge but no packages list, which pnpm 9+ requires
the moment a workspace file exists at all, even for a single package.
Surfaced by the first real pipeline run (frontend-prepare failed with
"packages field missing or empty").
This commit is contained in:
Sluijsens
2026-07-29 14:36:10 +02:00
parent 2cd8c4aa88
commit ff0fc66b10
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidlc-docs/features/gitea-deployment-workflow/audit.md
+10
View File
@@ -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)
---
## 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
---