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

@Kelsey-Ethyca Kelsey-Ethyca marked this pull request as ready for review November 19, 2025 21:35
@vercel
Copy link

vercel bot commented Nov 19, 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 Preview Nov 19, 2025 9:43pm
fides-privacy-center Ignored Ignored Nov 19, 2025 9:43pm

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Nov 19, 2025

Greptile Summary

  • Updated Unreleased comparison link and added new 2.75.0 release section header
  • Contains formatting issues: duplicate "Fixed" and "Changed" sections need consolidation
  • Minor typo: "ansync" should be "async" on line 48

Confidence Score: 3/5

  • This PR is safe to merge after fixing the formatting issues
  • The changes correctly update the version header structure, but there are organizational issues with duplicate sections and a typo that should be addressed before merging to maintain changelog quality
  • CHANGELOG.md requires attention for duplicate sections and typo correction

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.

Additional Comments (2)

  1. CHANGELOG.md, line 48 (link)

    syntax: typo: "ansync" should be "async"

  2. CHANGELOG.md, line 52-72 (link)

    style: duplicate sections: there are two "### Fixed" sections (lines 52 and 68) and two "### Changed" sections (lines 43 and 71) in the 2.75.0 release. Consolidate these - each section type should appear only once per release. Move the entries from lines 68-72 to their respective sections earlier in the release.

1 file reviewed, 2 comments

Edit Code Review Agent Settings | Greptile
React with 👍 or 👎 to share your feedback on this new summary format

@Kelsey-Ethyca Kelsey-Ethyca added this pull request to the merge queue Nov 19, 2025
Merged via the queue into main with commit a0a8754 Nov 19, 2025
41 checks passed
@Kelsey-Ethyca Kelsey-Ethyca deleted the update-changelog-release-2.75.0 branch November 19, 2025 22:13
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