You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revert feature flag to enable/disable content hash cleanup (#1966)
* Revert feature flag to enable/disable content hash cleanup
The `feature_stable_consent_hash_migration` feature flag was confusing, and setting the old hash to null provided no real value
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,9 +30,7 @@ Changes:
30
30
31
31
* Stabilized consent checks
32
32
* In order to make the consent hashes more robust, a more consistent way of hashing the user attributes has been introduced
33
-
* This feature automatically migrates from the old hashes to the new hashes, cleaning up the old hash.
34
-
* However, if blue/green deployments are used or if you want to keep the option open to roll back the EB release, keep the `feature_stable_consent_hash_migration` set to false in order to preserve the old consent hashes.
35
-
* Once the new release is fully rolled out, set `feature_stable_consent_hash_migration` to true. This will clean up the old consent hashes upon login. In the next EB release, the old consent hash column will be deleted.
33
+
* This feature automatically migrates from the old hashes to the new hashes upon login.
0 commit comments