Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
There was a problem hiding this comment.
Code Review: Release 2.83.0
This PR contains no code changes (0 additions, 0 deletions) — it is a release checklist PR for traceability purposes only and is explicitly marked as not to be merged.
There is nothing to review from a code standpoint. The PR serves as a process artifact to track manual pre-release and post-release verification steps (quickstart, test environment, API docs, CLI commands, Privacy Center, Admin UI, CHANGELOG, and post-release publishing verification).
No findings.
…ltering (#7868) Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7863 +/- ##
==========================================
+ Coverage 83.90% 85.15% +1.25%
==========================================
Files 627 627
Lines 40780 41020 +240
Branches 4742 4775 +33
==========================================
+ Hits 34215 34931 +716
+ Misses 5466 5019 -447
+ Partials 1099 1070 -29 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…7882) Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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:
nox -s quickstart(verify you can complete the interactive prompts from the command-line)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 thepullcommand to workfides user loginfides 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 containerfides scan dataset db --credentials-id app_postgresPrivacy Center
Admin UI
Documentation
Instead, they should be committed on a branch off of
mainand then PR'd and merged intomain, before being cherry-picked over to the release branch. This ensures that the CHANGELOG stays consistent between the release branch andmain.Publishing the release
When publishing the release, be sure to include the following sections in the release description:
## Release Pull Requestsection that includes a link back to the release PR (i.e., this one!) for tracking purposesPost-Release Steps