Release 2.22.1 #4316
Closed
Release 2.22.1 #4316
Conversation
This file contains 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
Co-authored-by: Dawn Pattison <pattisdr@users.noreply.github.com> Co-authored-by: Allison King <allison@ethyca.com> Co-authored-by: Allison King <allisonjuliaking@gmail.com> Co-authored-by: Andrew Jackson <andrew.c.j1995@gmail.com>
* feat: use a pydantic URL type for privacy policy URLs * fix: static_checks * fix: more tests, but still some failures on patching * fix: update other uses of invalid URLs in the tests * Update src/fides/api/schemas/privacy_experience.py Co-authored-by: Dawn Pattison <pattisdr@users.noreply.github.com> * fix: consent util tests * dummy commit --------- Co-authored-by: Dawn Pattison <pattisdr@users.noreply.github.com>
* init * feat: add non-dev-mode verification for IP addresses * fix: static_checks * feat: add tests * cleanup * feat: add better error messaging if the hostname can't resolve * fix: docstring * fix: handle special cases for templated values * feat: extract host checking and apply it to the authenticated client class * Fixing the values being passed into deny_unsafe_hosts and moving the check to before the send is executed * Removing unused import * Fixing typo and updating change log --------- Co-authored-by: Adrian Galvan <adrian@ethyca.com>
* feat: remove the config_read scope from the viewer role * feat: remove the CONFIG_READ scope from the contributor role as well
Co-authored-by: Kelsey Thomas <101993653+Kelsey-Ethyca@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. 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).
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-pickedover 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 Requestsection that includes a link back to the release PR (i.e., this one!) for tracking purposes## QA Touch Test Runsection that includes a link to the QATouch test run (QA team should provide this)Post-Release Steps
python3 -m venv 2_12_0_venvsource 2_12_0_venv/bin/activatepip install ethyca-fidesfides deploy up