@metasession.co/devaudit-cli 0.1.8 → 0.1.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@metasession.co/devaudit-cli",
3
- "version": "0.1.8",
3
+ "version": "0.1.9",
4
4
  "description": "DevAudit CLI — installs, syncs, and operates the Metasession SDLC across consumer projects.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -33,7 +33,7 @@
33
33
  },
34
34
  "dependencies": {
35
35
  "@clack/prompts": "^0.8.2",
36
- "@metasession.co/devaudit-plugin-sdk": "^0.1.8",
36
+ "@metasession.co/devaudit-plugin-sdk": "^0.1.9",
37
37
  "commander": "^12.1.0",
38
38
  "consola": "^3.2.3",
39
39
  "env-paths": "^3.0.0",
@@ -327,59 +327,18 @@ jobs:
327
327
  --category test_report ${FLAGS}
328
328
  fi
329
329
 
330
- # Upload compliance docs (planning category)
331
- for DOC in compliance/RTM.md compliance/test-plan.md compliance/test-cases.md; do
332
- if [ -f "$DOC" ]; then
333
- upload "$(basename "$DOC")" \
334
- {{PROJECT_SLUG}} _compliance-docs compliance_document "$DOC" \
335
- --category planning ${FLAGS}
336
- fi
337
- done
338
-
339
- # Upload release tickets (pending only approved releases are historical)
340
- for DIR in compliance/pending-releases; do
341
- if [ -d "$DIR" ]; then
342
- for TICKET in "$DIR"/*.md; do
343
- [ -f "$TICKET" ] || continue
344
- upload "$(basename "$TICKET")" \
345
- {{PROJECT_SLUG}} _compliance-docs compliance_document "$TICKET" \
346
- --category release_artifact ${FLAGS}
347
- done
348
- fi
349
- done
350
-
351
- # Upload per-requirement evidence — scoped to requirements with a
352
- # pending release ticket. Without this scoping every historical
353
- # compliance/evidence/REQ-*/ folder would be re-uploaded on every
354
- # run, re-populating the release-requirement matrix with the full
355
- # project catalogue (DevAudit #133).
356
- IN_SCOPE_REQS=()
357
- if [ -d compliance/pending-releases ]; then
358
- for TICKET in compliance/pending-releases/RELEASE-TICKET-REQ-*.md; do
359
- [ -f "$TICKET" ] || continue
360
- REQ_ID=$(basename "$TICKET" .md | sed 's/^RELEASE-TICKET-//')
361
- IN_SCOPE_REQS+=("$REQ_ID")
362
- done
363
- fi
364
-
365
- if [ ${#IN_SCOPE_REQS[@]} -eq 0 ]; then
366
- echo "No pending release tickets found — skipping per-requirement evidence upload"
367
- else
368
- echo "In-scope requirements for this release: ${IN_SCOPE_REQS[*]}"
369
- for REQ_ID in "${IN_SCOPE_REQS[@]}"; do
370
- REQ_DIR="compliance/evidence/${REQ_ID}/"
371
- if [ ! -d "$REQ_DIR" ]; then
372
- echo "Warning: pending ticket for ${REQ_ID} but no ${REQ_DIR} on disk"
373
- continue
374
- fi
375
- for ARTIFACT in "$REQ_DIR"*.md; do
376
- [ -f "$ARTIFACT" ] || continue
377
- upload "${REQ_ID}/$(basename "$ARTIFACT")" \
378
- {{PROJECT_SLUG}} "${REQ_ID}" compliance_document "$ARTIFACT" \
379
- --category planning ${FLAGS}
380
- done
381
- done
382
- fi
330
+ # NOTE: committed compliance docs (planning category: RTM/test-plan/
331
+ # test-cases, release tickets, and per-requirement
332
+ # compliance/evidence/REQ-*/ folders) are intentionally NOT uploaded
333
+ # here. compliance-evidence.yml is the single owner of those — it
334
+ # fires on every compliance/** push and uploads them to the same
335
+ # release (both workflows resolve the same version via
336
+ # derive-release-version.sh). Uploading them here too meant any push
337
+ # touching both code and compliance/ ran both workflows and inserted
338
+ # a duplicate row for every doc (evidence is append-only, no upsert),
339
+ # and re-populated the release matrix with the full catalogue. This
340
+ # job now uploads ONLY run-generated gate evidence (security_scan /
341
+ # ci_pipeline / test_report) above. See issue #45.
383
342
 
384
343
  if [ "$UPLOAD_FAILURES" -gt 0 ]; then
385
344
  echo "::error::${UPLOAD_FAILURES} evidence upload(s) failed — release is missing gate evidence and cannot pass UAT review"