Skip to content

Restore strict frontend CI build checks in Build & Docker Verification#1

Merged
FearSmoker merged 2 commits into
mainfrom
copilot/fix-build-docker-verification
Jun 9, 2026
Merged

Restore strict frontend CI build checks in Build & Docker Verification#1
FearSmoker merged 2 commits into
mainfrom
copilot/fix-build-docker-verification

Conversation

Copilot AI commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

The Build & Docker Verification job was failing due to frontend warnings being escalated to errors in CI. The workflow had been temporarily configured to bypass this behavior, which masked real compile/lint regressions in the build stage.

  • Problem addressed

    • Removed the CI warning-suppression workaround from the frontend production build step so the job reflects actual build health.
  • Workflow change

    • Updated .github/workflows/ci.yml to run npm run build under normal CI semantics (no CI=false override).
  • Net effect

    • The pipeline now correctly fails when frontend warnings/errors would break production builds, instead of silently passing that stage.
- name: Compile Frontend Production Build
  run: |
    cd client
    npm run build

@FearSmoker FearSmoker marked this pull request as ready for review June 9, 2026 06:22
Copilot AI changed the title [WIP] Fix failing GitHub Actions job Build & Docker Verification Restore strict frontend CI build checks in Build & Docker Verification Jun 9, 2026
Copilot AI requested a review from FearSmoker June 9, 2026 06:25
@FearSmoker FearSmoker merged commit db46faa into main Jun 9, 2026
2 checks passed
@FearSmoker FearSmoker deleted the copilot/fix-build-docker-verification branch June 9, 2026 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants