-
Draft: Remove npm_allow_packages_in_multiple_projects feature flag 0 of 1 checklist item completedgitlab!112784 17.1Category:Package Registry Package:P2 SLONear Miss Stretch [deprecated] Accepting merge requests automation:ml backend customer devopspackage feature flag grouppackage registry missed:15.10 missed:15.11 missed:15.9 missed:16.0 missed:16.1 missed:16.10 missed:16.11 missed:16.2 missed:16.3 missed:16.4 missed:16.5 missed:16.6 missed:16.7 missed:16.8 missed:16.9 missed:17.0 npm Registry priority2 rails ruby sectionci severity2 typebug workflowin dev
-
-
Protected containers: Use can_admin_all_resources? instead of user.admin? ContainerRegistryAuthService 4 of 5 checklist items completed
-
Small improvements to Container Registry index docs 0 of 13 checklist items completed
-
Protected packages: Collection of wording changes 4 of 5 checklist items completed
-
Draft: fix: Allow access tokens in headers to access debian packages 0 of 1 checklist item completed
-
Docs: Make it clear that Registry Metadata database is not provisioned automatically 4 of 16 checklist items completed
-
-
-
gitlab!153521 17.1
-
-
Draft: refactor: Fix rubocop issues related to ContainerRegistryAuthService 4 of 10 checklist items completed
-
Protected packages: REST API DELETE package protection rules 6 of 11 checklist items completed
-
Protected containers: Update protection rules in project settings ui 8 of 8 checklist items completed
-
Draft: Protected packages: Use positive logic to protected_up_to_access_level 11 of 11 checklist items completed
-
gitlab!148665 17.1
-
Protected packages: REST API POST package protection rule 6 of 11 checklist items completed