-
Notifications
You must be signed in to change notification settings - Fork 121
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
Deploy RC 240 to Prod #7568
Merged
Merged
Deploy RC 240 to Prod #7568
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
changelog: Internal, Attempts API, Standardize events
changelog: Internal, Health Checks, Remove account reset health check
changelog: Internal, Database Optimization, Avoid double-update to doc_auth_logs table
changelog: Internal, Background Jobs, Update GoodJob and remove concurrency controls
changelog: Internal, Dependencies, Update pg gem dependency
changelog: Internal, Background Jobs, Move Account Reset job to long running queue
changelog: Bug Fixes, Identity Verification, Remove ThreatMetrix review redirects
* Remove ThreatMetrix deactivation changelog: Bug Fixes, Identity Verification, Remove ThreatMetrix deactivation * remove specs
There were 2 feature flags for ThreatMetrix behavior that conflicted: - `proofing_device_profiling_decisioning_enabled`: This determined whether or not a user saw the "sad face" screen - `lexisnexis_threatmetrix_required_to_verify`: This determined whether or not a user received an active profile after successful proofing There is no case where we want one and not the other or vice versa. Thus this commit merges them into a single `lexisnexis_threatmetrix_required_to_verify` config. [skip changelog]
Updated in the draft release notes |
mitchellhenke
approved these changes
Jan 3, 2023
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.
Internal