chore: apply 51278a70d remediations onto origin/main#854
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThe PR updates Playwright Chromium settings, UI and regression-test expectations, sitemap checks, and Supabase schema validation. The drift manifest reflects current database objects, while tests now verify revised form provenance, authentication gating, dashboard labeling, and interaction behavior. ChangesBrowser and regression contracts
Supabase schema contracts
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d701f2aac0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "postgres_image": "supabase/postgres:17.6.1.127", | ||
| "schema_sha256": "302a9ecec8e69564d50035be8480fa5e5686ca6136d96978f2188ecf5fb58be1", | ||
| "replay_seconds": 18, | ||
| "schema_sha256": "e93fe90cae38654e77b7be0f81e5a0c90b0c7db2fd37d76e32f4f52a089eff45", |
There was a problem hiding this comment.
Regenerate the drift manifest from the current schema
This changes the manifest hash to e93fe90c…, but the normalized hash of the checked-in supabase/schema.sql is still 302a9ece…; scripts/check-drift.ts explicitly fails fast when these differ. In any environment that runs the Supabase drift gate, this stale manifest blocks the check before live drift is compared, and the snapshot also omits objects still created by current migrations such as the registry projection and title-word artifacts. Regenerate supabase/drift-manifest.json from the current schema.
Useful? React with 👍 / 👎.
| .filter((fileName) => /^\d+_.+\.sql$/.test(fileName)) | ||
| .sort(); | ||
| expect(migrationFiles.at(-1)).toBe("20260717173000_reassert_supabase_admin_default_privileges.sql"); | ||
| expect(migrationFiles.at(-1)).toBe("20260717161000_assert_supabase_admin_default_privileges.sql"); |
There was a problem hiding this comment.
Keep the final migration guard aligned with migrations
The migrations directory still sorts to 20260717173000_reassert_supabase_admin_default_privileges.sql, so this reverted assertion now fails in tests/supabase-schema.test.ts before the Supabase replay guards can pass. This same stale-schema pattern shows up later in the file as well, where the updated assertions reject the current pg_catalog.to_jsonb(old) cleanup function and require corrector guards that are not present in the final schema. Update the expected guard to the actual final migration/schema state or include the missing SQL changes.
Useful? React with 👍 / 👎.
| expect(data.publicRouteHandlers).toContainEqual({ route, file }); | ||
| expect(data.apiRoutes).not.toContainEqual({ route, file }); | ||
| expect(data.redirects).toContainEqual({ route, file, target }); | ||
| expect(productSection).toContain(`\`${route}\``); |
There was a problem hiding this comment.
Assert redirect handlers in the redirect section
The generated site map lists /applications, /differentials/presentations, and /medications under ## Redirects, and the existing test immediately above already asserts they are not in productSection. This added duplicate test expects the opposite, so tests/site-map.test.ts fails for these valid redirect-only routes; assert against the redirect section or remove the duplicate block.
Useful? React with 👍 / 👎.
Summary
51278a70dremediation set ontoorigin/mainwhile preserving currentmainbehavior.d8739ed02) with no runtime code changes beyond the reviewed remediation scope.Verification
npm run verify:pr-localduring local iteration (initially blocked by missingprettier/toolchain modules in this worktree; rerun pending full toolchain install).npm run verify:cheap(runtime portion passed; final gate failed at tooling stage:scripts/generate-site-map.tscould not resolveprettierin this checkout).npm run verify:uiwhen UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changedplaywright.config.ts) blocked production/advisory UI lanes; hosted UI checks were re-run after this fix to refresh before merge.npm run verify:releasebefore release or handoff confidence claimsFor retrieval, ranking, selection, chunking, source/citation rendering, or answer-contract changes,
verify:pr-localrunseval:rag:offlineautomatically.npm run check:production-readinesswhen clinical workflow, privacy, Supabase, source governance, or deployment behavior changednpm run check:deployment-readinesswhen deployment startup, hosting, or rollout behavior changedRisk and rollout
d8739ed02and re-rungh pr checkoutplus smoke checks; no data migrations or schema changes shipped.Clinical Governance Preflight
Clinical KB Database(sjrfecxgysukkwxsowpy)Notes
prettier) in this worktree; all required checks will be revalidated by hosted CI after fix.Summary by CodeRabbit
Accessibility
Bug Fixes
Tests