Fides 2.77.0 release notes

• 2.77.0: January 12, 2026

Helios

Detect and classify global data risks with comprehensive visualization for data mapping and reporting for modern Enterprise.

• Action Center Enhancements (Beta): The data discovery Action Center continues to evolve with improved workflow capabilities:
  • Multi-Select in Data Explorer: Users can now select multiple resources in the schema tree using Ctrl/Cmd+Click or Shift+Click, enabling faster bulk operations.
  • Ignore & Restore from Tree View: Resources can be ignored or restored directly from the schema explorer tree, making it easier to manage which resources require attention. Ignored resources appear with reduced opacity and hidden status indicators.
  • Updated Status Labels: Refined status labels for clearer resource state indication.
  • Keyboard Shortcut Fix: Fixed an issue where the "/" hotkey for focusing search would open Firefox's Quick Find instead.
• LLM Classifier Improvements: Several enhancements improve the reliability and accuracy of automated data classification:
  • Improved Error Handling: Better handling of transient errors during LLM classification prevents unnecessary failures.
  • Token Limit Restored: The default max_tokens setting has been restored to 8192 (from 1200) for improved classification accuracy.
  • Rationale Truncation: Classification rationales are now limited to 500 characters to prevent storage issues.
  • Edge Case Fix: Fixed classification issues with inactive and non-defaulted data categories.
• Detection & Discovery Fixes:
  • Fixed detection results persisting incorrectly for non-database Datastore monitors.
  • Fixed Salesforce detection incorrectly promoting staged resources.
• Terminology Update: The terminology for reviewed resources has been updated from "approve/unapprove" to "review/unreview" across all discovery monitor APIs for clarity.
• System Inventory: Fixed bulk delete modal not closing after deleting multiple systems.

Lethe

Enterprise grade privacy request management and processing with a single orchestration layer for DSRs across vendors and systems

• New Request Manager (General Availability): The redesigned privacy request manager is now the default experience, replacing the previous table-based view. The new interface provides:
  • Modern List-Based Design: Improved visual hierarchy and information density for faster request processing.
  • Location Filtering: Filter requests by geographic location.
  • Enhanced Sorting: Sort requests by multiple criteria to prioritize work.
  • Filter-Based Bulk Actions: Bulk operations now accept filter sets in addition to explicit ID lists, enabling true "select all" functionality across your entire filtered result set. This allows you to approve, deny, retry, cancel, or delete all matching requests at once—even across pages.

Janus

High performance consent recording and orchestration for data sharing, built for enterprise data engineering and AI pipelines.

• Customizable GPC Translation Fields: Privacy experiences now support fully customizable Global Privacy Control (GPC) text fields. Administrators can tailor all GPC-related messaging in consent banners and modals, including the GPC label, title, description, and status labels (e.g., "GPC Applied" or "GPC Overridden"). This gives customers complete control over how GPC signals are communicated to end users, supporting brand consistency and regulatory requirements across different regions.
• Gzip Compression for Consent Cookies: FidesJS now supports optional gzip compression for consent cookies, significantly reducing cookie size for TCF implementations with large vendor lists.
  • This is especially valuable for sites approaching browser cookie size limits.
  • The compression uses the browser's native CompressionStream API with automatic fallback for unsupported browsers.
  • Full backward compatibility is maintained with existing cookies.
  • How to Enable: Set the fidesCookieCompression option to "gzip" in your FidesJS configuration, or set the FIDES_COOKIE_COMPRESSION environment variable for Privacy Center deployments.
• TCF Compliance Improvements: Several enhancements improve compliance with the Transparency and Consent Framework:
  • TCF Spec 2.3 Compliance: TC strings now always include the DisclosedVendors segment as required by TCF specification 2.3.
  • Special-Purpose Vendor Fix: Fixed an issue where vendors declaring only special purposes weren't being properly included in legitimate interest vendor bits for reject-all scenarios.
  • TC String Encoding Fix: Resolved a padding bug that added extra bytes to reject-all TC strings.
  • Custom Notices Fix: Fixed an issue where TCF consent preferences weren't being saved to preference history when custom privacy notices were also configured in the same experience.
• Consent Reporting Enhancement: The Consent Report CSV export now includes a "URL Recorded" column, making it easier to track which pages consent was collected from.
• V3 Consent APIs (Preview): Work continues on our next-generation consent APIs with several new capabilities:
  • Prefer Opt-In Policy: Added a new propagation policy that intelligently cascades preferences between parent and child notices—when a user opts into a child notice, the parent is automatically opted in, and all children are opted out only when the parent is explicitly opted out.
  • Enhanced Validation: Added validation for notice_history_id and experience_config_history_id against historical records, ensuring data integrity.
  • Response Control: New response_notice_keys parameter allows filtering which notice keys are returned when creating preferences.
  • Descendant Control: The current preferences endpoint now only includes child notices when include_descendants is explicitly set to true, giving more control over API response size.
  • Performance: GET endpoints now use read-only database connections for improved scalability.

Integrations

• New Integrations:
  • Medallia: New SaaS integration supporting access requests via Medallia's Customer TX query endpoint. The integration dynamically discovers PII fields from your Medallia schema.
  • Loop Returns: New integration for the Loop Returns platform, enabling DSR support for e-commerce returns data.
• SaaS Dataset Customization: Customer changes to SaaS integration datasets are now preserved across Fides upgrades. When you add custom fields, modify data categories, or update field metadata, those changes will be merged with future integration updates rather than overwritten. This eliminates the need to reapply customizations after each upgrade.

Fides core

• Security Headers: Recommended security headers can now be enabled for the Admin UI and Fides API, including X-Content-Type-Options, Strict-Transport-Security, Content-Security-Policy, and X-Frame-Options. Enable this feature by setting FIDES__SECURITY__HEADERS_MODE="recommended".
• Performance Improvements: The default async database pool size has been increased to 50 pooled connections and 50 overflow connections, improving performance for high-volume deployments.
• Taxonomy Enhancements:
  • Active taxonomy is now tracked in the URL, making it easier to share and bookmark specific taxonomy views.
  • New endpoint exposes taxonomy audit logs for compliance tracking.
  • Taxonomy audit logging now captures custom field changes.
• Bug Fixes:
  • Fixed an issue where repeatedly clicking "Delete" on custom fields would cause multiple errors.
  • Improved handling for page-level errors across the Admin UI.

Notes

This release marks the general availability of the new Request Manager UI. If you've been using the beta version, no action is required—the transition is automatic. Users of the previous request manager should find all familiar functionality in the new interface with an improved user experience.

The V3 Consent APIs continue in preview, with additional features shipping in upcoming releases as part of our ongoing consent platform evolution.