Release 2.78.1

[JadeCara]

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)

Next, run the following checks via the test environment:

API

• Verify that the generated API docs are correct @ http://localhost:8080/docs

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

• Verify the ethyca-fides release is published to PyPi: https://pypi.org/project/ethyca-fides/#history
• Verify the fides release is published to DockerHub: https://hub.docker.com/r/ethyca/fides
• Verify the fides-privacy-center release is published to DockerHub: https://hub.docker.com/r/ethyca/fides-privacy-center
• Verify the fides-sample-app release is published to DockerHub: https://hub.docker.com/r/ethyca/fides-sample-app

[vercel]

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

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ignored	Preview	Feb 5, 2026 2:10am
fides-privacy-center	Ignored		Feb 5, 2026 2:10am

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.36%. Comparing base (0f56643) to head (a0c4a31).

Additional details and impacted files

@@               Coverage Diff                @@
##           release-2.78.0    #7316    +/-   ##
================================================
  Coverage           85.35%   85.36%            
================================================
  Files                 540      539     -1     
  Lines               36294    35981   -313     
  Branches             4303     4230    -73     
================================================
- Hits                30979    30714   -265     
+ Misses               4357     4320    -37     
+ Partials              958      947    -11     

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

[greptile-apps]

Greptile Overview

Greptile Summary

This release PR (2.78.1) contains a single bug fix that explicitly sets the USER environment variable to fidesuser in the Dockerfile to prevent getpwuid() crashes when running containers with non-default UIDs.

• Added ENV USER=fidesuser after switching to the fidesuser account in the Dockerfile
• Included appropriate changelog entry documenting the change
• The fix addresses ENG-2517 and improves container stability when running with custom user IDs

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is a small, well-understood bug fix that adds a single environment variable to prevent crashes. The fix is properly documented in the changelog, and the PR has passed all release checklist items including quickstart verification, API docs, CLI commands, Privacy Center, Admin UI, and documentation checks.
• No files require special attention

Important Files Changed

Filename	Overview
Dockerfile	Added USER environment variable to prevent getpwuid() crashes with non-default UIDs
changelog/7315.yaml	Added changelog entry documenting the USER environment variable change

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}