Skip to content

Conversation

@Kelsey-Ethyca
Copy link
Contributor

Steps to Confirm

  1. check spelling and formatting

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 4, 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 4, 2025 3:30pm
fides-privacy-center Ignored Ignored Dec 4, 2025 3:30pm

@Kelsey-Ethyca Kelsey-Ethyca marked this pull request as ready for review December 4, 2025 15:35
@Kelsey-Ethyca Kelsey-Ethyca added this pull request to the merge queue Dec 4, 2025
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Dec 4, 2025

Greptile Overview

Greptile Summary

This PR updates the CHANGELOG.md to prepare for the 2.76.0 release. The changes include:

  • Updated the Unreleased section comparison link from 2.75.2..main to 2.76.0..main
  • Added a new 2.76.0 section with comparison link 2.75.2..2.76.0
  • All existing changelog entries for version 2.76.0 remain unchanged

The formatting is consistent with the established changelog format, spelling is correct, and the version comparison links are accurate.

Confidence Score: 5/5

  • This PR is safe to merge with no risk
  • This is a routine CHANGELOG update for a release version bump. The changes are minimal (only 3 lines modified), follow the established format perfectly, and contain no logic changes or code modifications. The version comparison links are correct, and all spelling/formatting is accurate.
  • No files require special attention

Important Files Changed

File Analysis

Filename Score Overview
CHANGELOG.md 5/5 Standard CHANGELOG update for 2.76.0 release with correct formatting and version links

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

Merged via the queue into main with commit 2832dea Dec 4, 2025
41 checks passed
@Kelsey-Ethyca Kelsey-Ethyca deleted the update-changelog-release-2.76.0 branch December 4, 2025 15:41
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