Fix false “no unit-test or coverage files found” failure in release Unit Tests job

[Copilot]

The release workflow’s Unit Tests job was failing despite Vitest passing and generating reports. The failure came from the artifact-presence guard in release.yml, not from Vite/Vitest output generation itself.

• Root cause

  • In .github/workflows/release.yml, the guard used:
    • find builds -type f | grep -q . under set -o pipefail
  • grep -q exits early after first match, which triggers a broken pipe on find (find: write error), making the pipeline non-zero and falsely tripping the failure path.

• Fix

  • Replaced the pipe-based check with a single-process-safe probe:
    • if [ -z "$(find builds -type f -print -quit)" ]; then ... fi
  • This preserves the intended behavior (fail only when builds/ is truly empty) and removes pipefail/SIGPIPE flakiness.

• Config alignment review (no code changes)

  • Verified vitest.config.js already targets builds/coverage and builds/test-results with configured reporters/output files.
  • Verified release/deploy report publishing flow remains aligned with existing docs/report upload patterns.

# before
if ! find builds -type f | grep -q .; then
  echo "::error::No unit-test or coverage files found under builds/ — check vitest/coverage configuration."
  exit 1
fi

# after
if [ -z "$(find builds -type f -print -quit)" ]; then
  echo "::error::No unit-test or coverage files found under builds/ — check vitest/coverage configuration."
  exit 1
fi

[github-actions]

🏷️ Automatic Labeling Summary

This PR has been automatically labeled based on the files changed and PR metadata.

Applied Labels: size-xs

Label Categories

• 🗳️ Content: news, dashboard, visualization, intelligence
• 💻 Technology: html-css, javascript, workflow, security
• 📊 Data: cia-data, riksdag-data, data-pipeline, schema
• 🌍 I18n: i18n, translation, rtl
• 🔒 ISMS: isms, iso-27001, nist-csf, cis-controls
• 🏗️ Infrastructure: ci-cd, deployment, performance, monitoring
• 🔄 Quality: testing, accessibility, documentation, refactor
• 🤖 AI: agent, skill, agentic-workflow

For more information, see .github/labeler.yml.

[github-actions]

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

[Copilot]

Pull request overview

This PR updates the release workflow’s Unit Tests job to avoid a false failure caused by a find | grep -q guard running under set -o pipefail, where grep -q can terminate early and trigger a broken pipe error.

Changes:

• Replaced the pipe-based “any files under builds/” check with a find ... -print -quit probe to avoid SIGPIPE/pipefail flakiness.