Skip to content

fix: apply current migrations in e2e jobs - #79

Merged
Henrisal merged 1 commit into
mainfrom
fix/e2e-current-migrations
Oct 17, 2026
Merged

Henrisal merged 1 commit into
mainfrom
fix/e2e-current-migrations

Conversation

@Henrisal

Copy link
Copy Markdown
Contributor

pnpm run setup resets the database with graphile-migrate reset, which applies committed migrations only. The e2e jobs therefore ran against a schema without migrations/current/, so any PR whose frontend queries a field added there failed nearly every spec with a GraphQL 400 (Cannot query field "highlightText" on type "Event" on feat/nattitapahtuma, registrationProfile / prefill on feat/prefill). Unit tests were unaffected because their setup applies current/ itself.

Run pnpm --filter @app/db run watch --once after setup in all three e2e jobs so the e2e database matches what pnpm dev gives locally.

🤖 Generated with Claude Code

pnpm run setup resets the database to committed migrations only, so
e2e ran against a schema without migrations/current/. Any PR whose
frontend queries a field added there failed every spec with a GraphQL
400. Run watch --once after setup in each e2e job.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

📦 Next.js Bundle Analysis for @app/client

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@Henrisal
Henrisal merged commit 907ac21 into main Oct 17, 2026
14 checks passed
@Henrisal
Henrisal deleted the fix/e2e-current-migrations branch October 17, 2026 13:18
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