Skip to content

Conversation

@lucanovera
Copy link
Contributor

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
Copy link

vercel bot commented Dec 3, 2025

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

2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
fides-plus-nightly Ignored Ignored Dec 3, 2025 9:03pm
fides-privacy-center Ignored Ignored Dec 3, 2025 9:03pm

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Dec 3, 2025

Greptile Overview

Greptile Summary

This PR adds a changelog entry for version 2.57.2, which documents the security-focused upgrade of NextJS and React dependencies in the Privacy Center to address a React Server vulnerability (PR #7061). The change also correctly updates the version comparison link for 2.58.0 to reference 2.57.2 as the base version instead of 2.57.1.

The changes are:

  • Added new ## [2.57.2] section with Security subsection
  • Updated 2.58.0 compare link from 2.57.1...2.58.0 to 2.57.2...2.58.0

This is a standard changelog maintenance task that properly documents a patch release focused on security updates.

Confidence Score: 5/5

  • This PR is safe to merge with no risk - it's a straightforward changelog documentation update
  • Score reflects the minimal scope and risk of this change. The PR only updates CHANGELOG.md to document an already-merged security fix, adds proper version sequencing, and updates comparison links correctly. No code changes, no functional impact, and follows standard changelog conventions.
  • No files require special attention

Important Files Changed

File Analysis

Filename Score Overview
CHANGELOG.md 5/5 Added version 2.57.2 changelog entry documenting NextJS and React security upgrades, and updated 2.58.0 compare link to reference 2.57.2 as base

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 file reviewed, no comments

Edit Code Review Agent Settings | Greptile

@lucanovera lucanovera enabled auto-merge December 3, 2025 21:11
@lucanovera lucanovera added this pull request to the merge queue Dec 3, 2025
Merged via the queue into main with commit 71a325f Dec 3, 2025
41 checks passed
@lucanovera lucanovera deleted the update-changelog-release-2.57.2 branch December 3, 2025 21:26
lucanovera added a commit that referenced this pull request Dec 3, 2025
jjdaurora pushed a commit that referenced this pull request Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants