Repository navigation
feat(data-retention): workspace-level overrides for retention and PII - #5186
Merged
Merged
Conversation
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.
Summary
organization.dataRetentionSettingsJSON (no migration); resolved by a newresolveEffectiveRetentionHourshelper in the cleanup dispatcher's per-workspace path. Non-enterprise plans and the cleanup jobs themselves are unchanged.Type of Change
Testing
type-check0 errors,bun run lint16/16,check:api-validation:strictpassed,check:migrations origin/staging(no new migrations)resolveEffectiveRetentionHours(inherit / override / forever / scoping) and the retention-override contract schema (dedup refine, hour bounds) — 21 passingChecklist