Skip to content

Release 2.63.2#6224

Closed
erosselli wants to merge 6 commits intorelease-2.63.1from
release-2.63.2
Closed

Release 2.63.2#6224
erosselli wants to merge 6 commits intorelease-2.63.1from
release-2.63.2

Conversation

@erosselli
Copy link
Copy Markdown
Contributor

@erosselli erosselli commented Jun 12, 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. Some of these steps are redundant with automated tests, while others are only tested here as part of this check.

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

Additionally, there is a robust Release Process page available in Confluence (internal only).

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)
  • Have Roger run a QATouch automation run

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
  • DSR approval succeeds
  • DSR execution succeeds

User Permissions

  • Verify user creation
  • Verify a Viewer can view all systems
  • Verify a Data Steward can edit systems they are assigned

Documentation

  • Verify that the CHANGELOG is formatted correctly and clean up verbiage where needed
  • Verify that the CHANGELOG is 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
  • ## QA Touch Test Run section that includes a link to the QATouch test run (QA team should provide this)

Post-Release Steps

@erosselli erosselli added the do not merge Please don't merge yet, bad things will happen if you do label Jun 12, 2025
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Jun 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
fides-plus-nightly ⬜️ Ignored (Inspect) Visit Preview Jun 16, 2025 8:30pm
fides-privacy-center ⬜️ Ignored (Inspect) Jun 16, 2025 8:30pm

@cypress
Copy link
Copy Markdown

cypress Bot commented Jun 16, 2025

fides    Run #12997

Run Properties:  status check passed Passed #12997  •  git commit e26e186de0: ENG-725 Add settings for read-only Redis and for test Redis index (#6217)
Project fides
Branch Review release-2.63.3
Run status status check passed Passed #12997
Run duration 00m 52s
Commit git commit e26e186de0: ENG-725 Add settings for read-only Redis and for test Redis index (#6217)
Committer erosselli
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 5
View all changes introduced in this branch ↗︎

@codecov
Copy link
Copy Markdown

codecov Bot commented Jun 16, 2025

Codecov Report

❌ Patch coverage is 97.72727% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 86.91%. Comparing base (26fcc2e) to head (e26e186).

Files with missing lines Patch % Lines
src/fides/api/util/cache.py 94.73% 0 Missing and 1 partial ⚠️

❌ Your patch status has failed because the patch coverage (97.72%) is below the target coverage (100.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@                Coverage Diff                 @@
##           release-2.63.1    #6224      +/-   ##
==================================================
+ Coverage           86.90%   86.91%   +0.01%     
==================================================
  Files                 439      439              
  Lines               27093    27129      +36     
  Branches             2934     2937       +3     
==================================================
+ Hits                23544    23580      +36     
  Misses               2906     2906              
  Partials              643      643              

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

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.

4 participants