ENG-3430: make privacy center actions optional

[nreyes-dev]

Ticket ENG-3430

Description Of Changes

Privacy Center fails to start when config.json has an empty actions array (or omits it entirely). This blocks customers who only use Privacy Center to serve fides.js and don't need DSR action tiles. This change makes actions optional, defaulting to [].

Code Changes

• Removed the non-empty array validation check for actions in the Privacy Center config validator
• Made actions optional (defaulting to []) in the PrivacyCenterConfig and PartialPrivacyCenterConfig Pydantic schemas
• Updated TypeScript types (Config, LegacyConfig, API PrivacyCenterConfig) to mark actions as optional
• Added ?? [] guards where components iterate over config.actions

Steps to Confirm

Config file path:

1. Set "actions": [] in clients/privacy-center/config/config.json
2. Start the Privacy Center — it should load without errors
3. The home page should render with no action tiles (consent card still appears if configured)

API config path:

1. Create/update a property via the API with privacy_center_config that has no actions key (or "actions": [])
2. Set USE_API_CONFIG=true and start the Privacy Center — it should load without errors

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]

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

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ignored	Preview	Apr 14, 2026 9:26pm
fides-privacy-center	Ignored		Apr 14, 2026 9:26pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.06%. Comparing base (330f838) to head (6c50c1d).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7919      +/-   ##
==========================================
- Coverage   85.06%   85.06%   -0.01%     
==========================================
  Files         629      629              
  Lines       40855    40855              
  Branches     4748     4748              
==========================================
- Hits        34753    34752       -1     
- Misses       5029     5030       +1     
  Partials     1073     1073              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Title	Lines	Statements	Branches	Functions
admin-ui		6.1% (2663/43652)	5.22% (1293/24750)	4.19% (542/12919)
fides-js		78.98% (1962/2484)	65.55% (1214/1852)	72.57% (336/463)
privacy-center		85.97% (331/385)	81.36% (179/220)	78.87% (56/71)

[jpople]

Code looks good, manually tested both API path and hardcoded config and privacy center loads as expected.