Update Changelog for release 2.82.1

[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 31, 2026 5:50pm
fides-privacy-center	Ignored		Mar 31, 2026 5:50pm

[claude]

Release Changelog PR — 2.82.0 → 2.82.1

This is a clean, straightforward release changelog consolidation. All individual YAML fragment files are correctly removed and their content is accurately reflected in CHANGELOG.md. The Unreleased comparison URL is correctly bumped to 2.82.1..main.

Two minor formatting nits noted inline:

1. Jira DSR entry line continuation — The multi-line bullet for #7772 has continuation lines at column 0. Should be indented 2 spaces to align under the bullet text (cosmetic only; renders fine as-is).

2. db-migration bare URL for #7788 — The label reference is a raw URL rather than a formatted Markdown link, which is inconsistent with the rest of the file's style.

No functional or content issues found — all entries correctly match their source YAML files. Good to merge once nits are addressed (or left as-is, both are cosmetic).

[claude]

The continuation lines of the Jira DSR lifecycle entry are not indented, which leaves them flush with column 0. While Markdown will still render this as a single bullet point, it makes the raw text harder to read. Consider indenting the continuation with two spaces to align them under the bullet text:

- Support Jira DSR lifecycle: auto-create ManualTaskConfig on jira_ticket
  connection setup, use pending_external status for Jira manual tasks,
  and treat pending_external equivalently to requires_input in watchdog
  and duplication detection. [#7772](https://github.com/ethyca/fides/pull/7772)

[claude]

The db-migration label is appended as a bare URL rather than a Markdown link. Other entries in this file (and the PR template) reference the label URL as a formatted link. Consider using:

- Added unique identity index to privacy_preferences_current partition [#7788](https://github.com/ethyca/fides/pull/7788) [![db-migration](https://github.com/ethyca/fides/labels/db-migration)](https://github.com/ethyca/fides/labels/db-migration)

or at minimum wrapping it as a plain Markdown link so it renders with a label rather than the raw URL.