Closed andres-torres-marroquin closed 3 weeks ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Passed #10723
•
34e00b157d: HJ-116 - Fix BigQuery `partitioning` queries to properly support multiple identi...
Project |
fides
|
Branch Review |
release-2.48.1
|
Run status |
Passed #10723
|
Run duration | 00m 38s |
Commit |
34e00b157d: HJ-116 - Fix BigQuery `partitioning` queries to properly support multiple identi...
|
Committer | Andres Torres |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
0
|
Skipped |
0
|
Passing |
4
|
⚠️ You've recorded test results over your free plan limit. Upgrade your plan to view test results. | |
View all changes introduced in this branch ↗︎ |
Attention: Patch coverage is 62.50000%
with 3 lines
in your changes missing coverage. Please review.
Project coverage is 83.86%. Comparing base (
4abb9e6
) to head (34e00b1
). Report is 24 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
src/fides/api/service/connectors/query_config.py | 40.00% | 3 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
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
@NevilleS: For this patch release, we've skipped the general checklist steps crossed out (~strikethrough~) below.
~From the release branch, confirm the following:~
~* [ ] Quickstart works:
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) ~* [ ] 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 thepull
command to workfides 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 containerfides scan dataset db --credentials-id app_postgres
Privacy Center
Admin UI
User Permissions
~- [ ] Verify user creation~ ~- [ ] Verify a Viewer can view all systems~ ~- [ ] Verify a Data Steward can edit systems they are assigned ~
Documentation
:warning: 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 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 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
python3 -m venv 2_12_0_venv
source 2_12_0_venv/bin/activate
pip install ethyca-fides
fides deploy up