FIDES-1977: 2.59.2

[tvandort]

• empty commit to start release 2.59.0
• LJ-678 Fix TCFConfiguration relationship definitions (LJ-678 Fix TCFConfiguration relationship definitions #6031)
• empty commit to start release 2.59.1
• LJ-683: Adds new embedded-consent route to PC (LJ-683: Adds new embedded-consent route to PC #6040)
• Fix: Ignore null fields from identity_inputs (Fix: Ignore null fields from identity_inputs #6045)
• LJ-553 - Adds an import that prevents errors (LJ-553 - Adds an import that prevents errors #6042)
• Celery worker tests (Celery worker tests #6058)
• Postgresql monitor. (Postgresql monitor. #6018)
• HA-635: Postgres Connector SSL Mode (HA-635: Postgres Connector SSL Mode #6068)
• Updated CHANGELOG.md for release 2.59.2 (Updated CHANGELOG.md for release 2.59.2 #6071)
• Cherry-picking consent model changes
• Cherry picking SSL mode for MySQL
• Fixing change log
• Use the serverside logger.
• With retry.
• Print error.
• Less magic, more naming.
• Restore rate limit.
• Remove {} experience unless valid.
• Remove import cycle.
• Add request id to headers.
• Logging context.
• Better logs in geolocation.
• Fides logging.
• Warn and better error message.
• Empty experience behavior.
• Conditionally swap empty experience behavior.
• HA-673 - Updating pymssql to latest version (HA-673 - Updating pymssql to latest version #6135)

Closes []

Description Of Changes

Write some things here about the changes and any potential caveats

Code Changes

• list your code changes here

Steps to Confirm

1. list any manual steps for reviewers to confirm the changes

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
• 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 Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fides-privacy-center	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 9, 2025 1:18pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	⬜️ Ignored (Inspect)	Visit Preview		May 9, 2025 1:18pm