Deprecate canDelete fields of ContainerRepository, ContainerRepositoryDetails and ContainerRepositoryTag
Deprecation Summary
In 16.7, we add a new userPermissions
field that contain permissions to users actions and replaces the field canDelete
for ContainerRepository
, ContainerRepositoryDetails
, and ContainerRepositoryTag
. In GitLab 18.0, the canDelete
field will be removed.
Breaking Change
This is a breaking change and the users will need to update their workflows from using canDelete
to userPermissions.destroyContainerRepository
for ContainerRepository
and ContainerRepositoryDetails
, and replace canDelete
to userPermissions.destroyContainerRepositoryTag
for ContainerRepositoryTag
.
Affected Topology
Both, self-managed and SaaS users are affected by this deprecation.
Affected Tier
All tiers.
Checklists
Labels
-
This issue is labeled deprecation, and with the relevant ~devops::
,~group::
, and~Category:
labels. -
This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.
Timeline
Please add links to the relevant merge requests.
- As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule:
14.8, 14.9, 14.10, 15.0
–14.8
is the third milestone preceding the major release):-
A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page. -
Documentation has been updated to mark the feature as deprecated.
-
-
On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post. - On the major milestone:
-
The deprecated item has been removed. -
If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.
-
Mentions
-
Your stage's stable counterparts have been @mentioned
on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.- To see who the stable counterparts are for a product team visit product categories
- If there is no stable counterpart listed for Sales/CS please mention
@timtams
- If there is no stable counterpart listed for Support please mention
@gitlab-com/support/managers
- If there is no stable counterpart listed for Marketing please mention
@cfoster3
- If there is no stable counterpart listed for Sales/CS please mention
- To see who the stable counterparts are for a product team visit product categories
-
Your GPM has been @mentioned
so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.
Deprecation Milestone
16.7
Planned Removal Milestone
18.0
Links
Edited by Pedro Pombeiro