Update CHANGELOG for release 2.81.0

[erosselli]

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]

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	Mar 12, 2026 4:18pm
fides-privacy-center	Ignored		Mar 12, 2026 4:18pm

[greptile-apps]

Greptile Summary

This PR aggregates 81 individual changelog YAML fragment files into CHANGELOG.md to cut the 2.81.0 release, covering ~55 entries across Added, Changed, Fixed, Removed, Security, and Developer Experience categories. The bulk of the diff is deletions of the consumed YAML fragments.

Key observations:

• The vast majority of entries are correctly formatted with accurate PR links and appropriate db-migration labels where applicable.
• changelog/ENG-2865.yaml had a never-updated placeholder description (Add changelog entry for ENG-2865) and pr: 0. The file was deleted without substituting a real description, meaning the ENG-2865 change is entirely absent from the 2.81.0 release notes.
• changelog/ENG-2175-redis-cluster-support.yaml also had pr: 0, but the CHANGELOG.md was manually corrected with the actual PR number ([#7487]).
• The entry for #7557 on line 107–108 renders with the PR link on its own indented line rather than inline, due to the source YAML using a block scalar (>). This is an inconsistency with every other entry in the file.
• This PR changes 82 files, which exceeds the team's 15-file PR guideline, though this is an expected pattern for a release aggregation PR.

Confidence Score: 3/5

• Safe to merge as a changelog-only PR, but has documentation quality gaps that reduce traceability for two entries.
• No code changes are included — this is purely a documentation/changelog aggregation PR. The content is mostly accurate and well-formed, but the ENG-2865 change is undocumented (placeholder yaml deleted without a real description), and the ENG-2799: Track consent status per-connection instead of per-system #7557 entry has a minor formatting inconsistency. These reduce documentation quality but do not affect runtime behavior.
• CHANGELOG.md lines 107–108 (malformatted ENG-2799: Track consent status per-connection instead of per-system #7557 entry) and the absence of any entry for ENG-2865.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds 2.81.0 release section with ~30 entries across Added/Changed/Fixed/Removed/Security/Developer Experience categories. Contains a malformatted entry at line 107-108 where the PR link for #7557 appears on a separate line instead of inline, and the ENG-2865 change is absent from the final changelog (the yaml was deleted but no description was provided in its place).
changelog/ENG-2865.yaml	Deleted yaml file contained a placeholder description ("Add changelog entry for ENG-2865") and pr: 0 that were never updated. The file was removed without substituting a real changelog entry, meaning the ENG-2865 change is undocumented in the release notes.
changelog/ENG-2175-redis-cluster-support.yaml	Deleted yaml file had pr: 0 placeholder, but the CHANGELOG.md was manually corrected to include the actual PR link (#7487). Description content is correct.
changelog/7557-per-connection-consent-tracking.yaml	Deleted yaml used a YAML block scalar (>) for its description, which caused the resulting CHANGELOG.md entry to render with the PR link on its own separate line (line 108), breaking consistency with all other entries in the file.

_{Last reviewed commit: 0028c38}

[greptile-apps]

Malformatted entry — PR link on separate line

The PR link [#7557] is on its own line (with a leading space) rather than inline at the end of the bullet. This is because the source YAML used a YAML block scalar (>), and the PR number and labels fields were appended separately. All other entries in this file have the PR link on the same line as the description.

Suggested change

	- Fixed consent status tracking to key per-connection (connection_config.key) instead of per-system (system.fides_key). This changes the key shape in the affected_system_status JSONB column; existing rows are not backfilled.
	[#7557](https://github.com/ethyca/fides/pull/7557)
	- Fixed consent status tracking to key per-connection (connection_config.key) instead of per-system (system.fides_key). This changes the key shape in the affected_system_status JSONB column; existing rows are not backfilled. [#7557](https://github.com/ethyca/fides/pull/7557)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[erosselli]

@greptile re-review