Skip to content

ci: add frontend build check to catch broken builds#65

Open
will-yuponce-db wants to merge 2 commits intomainfrom
feature/ci-build-check
Open

ci: add frontend build check to catch broken builds#65
will-yuponce-db wants to merge 2 commits intomainfrom
feature/ci-build-check

Conversation

@will-yuponce-db
Copy link
Contributor

Summary

  • Adds a frontend-build job to CI that runs yarn build (vite build) in parallel with existing jobs
  • Catches broken frontend builds early — recent code was committed that broke the UI because the build was never verified in CI
  • No dependencies on other jobs for fastest feedback

Test plan

  • Verify the new Frontend Build Check job appears in GitHub Actions
  • Confirm it runs in parallel with other jobs (no needs)
  • Intentionally break a build to verify it catches failures

Made with Cursor

Recent code was committed that broke the UI because vite build was never
run in CI. This adds a parallel frontend-build job that runs `yarn build`
to verify the frontend compiles successfully.

Co-authored-by: Cursor <cursoragent@cursor.com>
- Remove redundant string literal comparisons in uc-asset-lookup-dialog
  (enum values already match the strings, so TS narrowing flagged them)
- Widen navigateToEntity param to EnrichedSemanticLink for entity_name access
- Allow empty string in assignTargetType state union type

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

1 participant