-
Notifications
You must be signed in to change notification settings - Fork 84
Release 2.74.3 #6997
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.74.3 #6997
Conversation
Co-authored-by: Jason Gill <jason.gill@ethyca.com>
…ding request manager UI (#6964) Co-authored-by: Jade Wibbels <jade@ethyca.com>
Co-authored-by: Jade Wibbels <jade@ethyca.com>
Co-authored-by: Jade Wibbels <jade@ethyca.com>
Co-authored-by: JadeWibbels <jade.wibbels@gmail.com> Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> Co-authored-by: Jade Wibbels <jade@ethyca.com>
|
Deployment failed with the following error: View Documentation: https://vercel.com/docs/two-factor-authentication |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (84.61%) 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 @@
## main #6997 +/- ##
==========================================
- Coverage 87.30% 80.75% -6.55%
==========================================
Files 524 524
Lines 34355 34423 +68
Branches 3956 3974 +18
==========================================
- Hits 29992 27798 -2194
- Misses 3503 5748 +2245
- Partials 860 877 +17 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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