Skip to content

empty commit to start release 2.60.0#6082

Closed
Roger-Ethyca wants to merge 7 commits intomainfrom
release-2.60.0
Closed

empty commit to start release 2.60.0#6082
Roger-Ethyca wants to merge 7 commits intomainfrom
release-2.60.0

Conversation

@Roger-Ethyca
Copy link
Copy Markdown
Contributor

@Roger-Ethyca Roger-Ethyca commented Apr 23, 2025

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

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Apr 23, 2025

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 Apr 25, 2025 9:05pm
fides-privacy-center ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 25, 2025 9:05pm

@cypress
Copy link
Copy Markdown

cypress Bot commented Apr 23, 2025

fides    Run #12879

Run Properties:  status check passed Passed #12879  •  git commit 2a42212ed3: conditionally add TCF to the Experience type options (#6091)
Project fides
Branch Review release-2.60.0
Run status status check passed Passed #12879
Run duration 00m 50s
Commit git commit 2a42212ed3: conditionally add TCF to the Experience type options (#6091)
Committer Jason Gill
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
⚠️ You've recorded test results over your free plan limit.
Upgrade your plan to view test results.
View all changes introduced in this branch ↗︎

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.95%. Comparing base (353ada5) to head (2a42212).
Report is 13 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6082      +/-   ##
==========================================
+ Coverage   86.87%   86.95%   +0.07%     
==========================================
  Files         419      420       +1     
  Lines       25980    26007      +27     
  Branches     2827     2831       +4     
==========================================
+ Hits        22571    22615      +44     
+ Misses       2789     2770      -19     
- Partials      620      622       +2     

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

@tvandort tvandort changed the base branch from main to release-2.59.2 April 24, 2025 17:07
@tvandort tvandort requested a review from a team as a code owner April 24, 2025 17:07
@tvandort tvandort changed the base branch from release-2.59.2 to main April 24, 2025 17:07
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.

7 participants