Updates to GitLab's delayed deletion feature for projects and groups

Starting with GitLab 16.0, the delayed deletion feature will be enabled by default for all GitLab Ultimate and Premium customers to prevent accidental deletions of projects and groups, which have been a frequent and costly issue. Previously, immediate deletion was the default, requiring manual activation of deletion protection, but now the option to delete immediately from the Admin Area will be removed, and delayed deletion will be the standard for both SaaS and self-managed users. Self-managed users can set a deletion delay period of 1 to 90 days, while SaaS users will have a fixed 7-day retention period. Despite this default setting, users can still perform immediate deletions through a two-step process in the project or group settings, with projects being renamed automatically during the pending deletion state to allow immediate recreation with the same name. Future updates will include automatic renaming for groups during deletion. The API will be updated to align with these changes, removing specific parameters and requiring double confirmation for deletions. Feedback on these changes is encouraged to enhance the safety and effectiveness of the deletion process.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.