-
Notifications
You must be signed in to change notification settings - Fork 84
Release 2.76.1 #7107
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
Closed
Closed
Release 2.76.1 #7107
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-2.76.0 #7107 +/- ##
==================================================
- Coverage 87.38% 87.27% -0.12%
==================================================
Files 530 530
Lines 35490 34882 -608
Branches 4123 4039 -84
==================================================
- Hits 31013 30443 -570
+ Misses 3583 3555 -28
+ Partials 894 884 -10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Co-authored-by: Lucano Vera <lucanovera@live.com.ar> Co-authored-by: Jade Wibbels <jade@ethyca.com>
Co-authored-by: Jade Wibbels <jade@ethyca.com> Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: Jason Gill <jason.gill@ethyca.com>
Co-authored-by: Jason Gill <103820+gilluminate@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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