Skip to content

Conversation

@JadeCara
Copy link
Contributor

Ticket []

Description Of Changes

Code Changes

Steps to Confirm

Pre-Merge Checklist

  • Issue requirements met
  • All CI pipelines succeeded
  • CHANGELOG.md updated
    • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
    • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
    • Updates unreleased work already in Changelog, no new entry necessary
  • UX feedback:
    • All UX related changes have been reviewed by a designer
    • No UX review needed
  • Followup issues:
    • Followup issues created
    • No followup issues
  • Database migrations:
    • Ensure that your downrev is up to date with the latest revision on main
    • Ensure that your downgrade() migration is correct and works
      • If a downgrade migration is not possible for this change, please call this out in the PR description!
    • No migrations
  • Documentation:
    • Documentation complete, PR opened in fidesdocs
    • Documentation issue created in fidesdocs
    • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
    • No documentation updates required

@vercel
Copy link
Contributor

vercel bot commented Jan 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
fides-plus-nightly Error Error Jan 20, 2026 9:31pm
1 Skipped Deployment
Project Deployment Review Updated (UTC)
fides-privacy-center Ignored Ignored Jan 20, 2026 9:31pm

Request Review

@github-actions
Copy link

github-actions bot commented Jan 20, 2026

🔍 API Type Validation Results

⚠️ Type mismatches detected (non-blocking check)

Warning

88 missing fields detected! This usually means TypeScript types are out of sync.
Most likely fix: Regenerate the TypeScript types (see below).

🔧 To fix these issues:

cd clients
npm run openapi:generate
git add -A
git commit -m "chore: regenerate TypeScript types from OpenAPI schema"

⚠️ Important: Review the changes carefully before committing!

  • Check for breaking changes in existing types
  • Verify manual overrides are preserved
  • Test affected frontend components

📎 View full logs in artifacts

Validation Status:

  • Admin UI: ⚠️ 26 error(s), 19 warning(s)
  • Privacy Center: ⚠️ 76 error(s), 21 warning(s)

📎 View full validation logs

Click "Summary" → Download "api-type-validation-logs" artifact


🔧 Quick Fix:

cd clients
npm run openapi:generate
git add -A
git commit -m "chore: regenerate TypeScript types"

Jade Wibbels and others added 3 commits January 20, 2026 14:16
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.

5 participants