Skip to content

Release 2.83.0#7863

Open
Kelsey-Ethyca wants to merge 5 commits intomainfrom
release-2.83.0
Open

Release 2.83.0#7863
Kelsey-Ethyca wants to merge 5 commits intomainfrom
release-2.83.0

Conversation

@Kelsey-Ethyca
Copy link
Copy Markdown
Contributor

Release Checklist

The release checklist is a manual set of checks done before each release to ensure functionality of the most critical components of the application.

This checklist should be copy/pasted into the final pre-release PR, and checked off as you complete each step.

Warning

THIS RELEASE BRANCH PULL REQUEST SHOULD NOT BE MERGED! IT IS FOR TRACEABILITY PURPOSES ONLY!

Pre-Release Steps

General

From the release branch, confirm the following:

  • Quickstart works: nox -s quickstart (verify you can complete the interactive prompts from the command-line)
  • Test environment works: nox -s "fides_env(test)" (verify the admin UI on localhost:8080, privacy center on localhost:3001, CLI and webserver)

Next, run the following checks via the test environment:

API

CLI

Run these from within the test environment shell:

  • git reset --hard - Note: This is required for the pull command to work
  • fides user login
  • fides push src/fides/data/sample_project/sample_resources/
  • fides pull src/fides/data/sample_project/sample_resources/
  • fides evaluate src/fides/data/sample_project/sample_resources/
  • fides generate dataset db --credentials-id app_postgres test.yml - Note: Because the filesystem isn't mounted, the new file will only show up within the container
  • fides scan dataset db --credentials-id app_postgres

Privacy Center

  • Every navigation button works
  • DSR submission succeeds
  • Consent request submission succeeds

Admin UI

  • Every navigation button works
  • Login/logout succeeds
  • DSR approval succeeds
  • DSR execution succeeds

Documentation

  • Verify that the CHANGELOG is formatted correctly and representative of the actual changes

⚠️ Note that any updates that need to be made to the CHANGELOG should not be commited directly to the release branch.
Instead, they should be committed on a branch off of main and then PR'd and merged into main, before being cherry-picked over to the release branch. This ensures that the CHANGELOG stays consistent between the release branch and main.

Publishing the release

When publishing the release, be sure to include the following sections in the release description:

  • ## Release Pull Request section that includes a link back to the release PR (i.e., this one!) for tracking purposes

Post-Release Steps

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 8, 2026

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

Project Deployment Actions Updated (UTC)
fides-plus-nightly Ready Ready Preview, Comment Apr 9, 2026 11:12pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
fides-privacy-center Ignored Ignored Apr 9, 2026 11:12pm

Request Review

Copy link
Copy Markdown

@claude claude bot left a comment

Choose a reason for hiding this comment

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

Code Review: Release 2.83.0

This PR contains no code changes (0 additions, 0 deletions) — it is a release checklist PR for traceability purposes only and is explicitly marked as not to be merged.

There is nothing to review from a code standpoint. The PR serves as a process artifact to track manual pre-release and post-release verification steps (quickstart, test environment, API docs, CLI commands, Privacy Center, Admin UI, CHANGELOG, and post-release publishing verification).

No findings.

…ltering (#7868)

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@JadeCara JadeCara requested a review from a team as a code owner April 9, 2026 15:50
@JadeCara JadeCara requested review from JadeCara and removed request for a team April 9, 2026 15:50
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.15%. Comparing base (1426025) to head (94c35df).
⚠️ Report is 22 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7863      +/-   ##
==========================================
+ Coverage   83.90%   85.15%   +1.25%     
==========================================
  Files         627      627              
  Lines       40780    41020     +240     
  Branches     4742     4775      +33     
==========================================
+ Hits        34215    34931     +716     
+ Misses       5466     5019     -447     
+ Partials     1099     1070      -29     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jpople jpople requested a review from a team as a code owner April 9, 2026 17:12
@jpople jpople requested review from speaker-ender and removed request for a team April 9, 2026 17:12
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2026

Title Lines Statements Branches Functions
admin-ui Coverage: 7%
5.88% (2547/43315) 4.88% (1199/24530) 3.95% (508/12835)
fides-js Coverage: 78%
78.98% (1962/2484) 65.55% (1214/1852) 72.57% (336/463)
privacy-center Coverage: 88%
85.93% (330/384) 81.1% (176/217) 78.87% (56/71)

…7882)

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

4 participants