fides icon indicating copy to clipboard operation
fides copied to clipboard

empty commit to start release 2.61.0

Open Roger-Ethyca opened this issue 9 months ago • 3 comments

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:

  • [x] Quickstart works: nox -s quickstart (verify you can complete the interactive prompts from the command-line)
  • [x] Test environment works: nox -s "fides_env(test)" (verify the admin UI on localhost:8080, privacy center on localhost:3001, CLI and webserver)
  • [x] 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:

  • [x] git reset --hard - Note: This is required for the pull command to work
  • [x] fides user login
  • [x] fides push src/fides/data/sample_project/sample_resources/
  • [x] fides pull src/fides/data/sample_project/sample_resources/
  • [x] fides evaluate src/fides/data/sample_project/sample_resources/
  • [x] 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
  • [x] fides scan dataset db --credentials-id app_postgres

Privacy Center

  • [x] Every navigation button works
  • [x] DSR submission succeeds
  • [x] Consent request submission succeeds

Admin UI

  • [x] Every navigation button works
  • [x] DSR approval succeeds
  • [x] DSR execution succeeds

User Permissions

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

Documentation

  • [x] Verify that the CHANGELOG is formatted correctly and clean up verbiage where needed
  • [x] Verify that the CHANGELOG is representative of the actual changes

:warning: 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

Roger-Ethyca avatar May 07 '25 19:05 Roger-Ethyca

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

Name Status Preview Comments Updated (UTC)
fides-plus-nightly ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 9, 2025 7:10pm
fides-privacy-center ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 9, 2025 7:10pm

vercel[bot] avatar May 07 '25 19:05 vercel[bot]

fides    Run #12920

Run Properties:  status check passed Passed #12920  •  git commit 76c9a007da: HA-676 - Fixed a bug that prevented from showing all the integrations… (#6138)
Project fides
Branch Review release-2.61.0
Run status status check passed Passed #12920
Run duration 00m 52s
Commit git commit 76c9a007da: HA-676 - Fixed a bug that prevented from showing all the integrations… (#6138)
Committer Andrés Torres Marroquín
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 ↗︎

cypress[bot] avatar May 07 '25 20:05 cypress[bot]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 86.92%. Comparing base (eecd0c0) to head (76c9a00). :warning: Report is 276 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6131      +/-   ##
==========================================
+ Coverage   86.88%   86.92%   +0.03%     
==========================================
  Files         423      423              
  Lines       26113    26350     +237     
  Branches     2838     2865      +27     
==========================================
+ Hits        22689    22904     +215     
- Misses       2807     2822      +15     
- Partials      617      624       +7     

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

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

codecov[bot] avatar May 07 '25 20:05 codecov[bot]