Skip to content

Conversation

@JadeCara
Copy link
Contributor

@JadeCara JadeCara commented Dec 11, 2025

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

vercel bot commented Dec 11, 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 Dec 12, 2025 1:13pm
fides-privacy-center Ignored Ignored Dec 12, 2025 1:13pm

@JadeCara JadeCara changed the base branch from main to release-2.76.0 December 11, 2025 16:46
@JadeCara JadeCara added the do not merge Please don't merge yet, bad things will happen if you do label Dec 11, 2025
@codecov
Copy link

codecov bot commented Dec 11, 2025

Codecov Report

❌ Patch coverage is 85.71429% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 87.27%. Comparing base (3198809) to head (8c2b7e5).

Files with missing lines Patch % Lines
src/fides/api/service/connectors/http_connector.py 84.61% 2 Missing ⚠️
...dependencies/privacy_request/convenience_fields.py 83.33% 0 Missing and 2 partials ⚠️
Additional details and impacted files
@@                Coverage Diff                 @@
##           release-2.76.0    #7107      +/-   ##
==================================================
- Coverage           87.38%   87.27%   -0.12%     
==================================================
  Files                 530      530              
  Lines               35490    34882     -608     
  Branches             4123     4039      -84     
==================================================
- Hits                31013    30443     -570     
+ Misses               3583     3555      -28     
+ Partials              894      884      -10     

☔ 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.

JadeCara and others added 6 commits December 11, 2025 17:37
Co-authored-by: Lucano Vera <lucanovera@live.com.ar>
Co-authored-by: Jade Wibbels <jade@ethyca.com>
Co-authored-by: Jade Wibbels <jade@ethyca.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: Jason Gill <jason.gill@ethyca.com>
@lucanovera lucanovera closed this Dec 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Please don't merge yet, bad things will happen if you do

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants