S17 Phase 4: artifact writes (delete, bulk)
Summary
Artifact write endpoints for the management API, per ADR-009: delete, container tag mutations, and bulk delete on the format-specific artifact routes, extending the read surface from S17 Phase 3: format artifact reads (#312 - closed) • Hayley Swimelar.
Scope
- Single-artifact delete: images, packages, versions, files
- Container tag mutations: tag upsert with a digest body (the same upsert the push path performs) and untag
- Bulk delete at every collection boundary ADR-009 names:
DELETE .../images,.../images/:image_id/tags,.../packages,.../versions,.../files
Gated on
- S20 Lifecycle management (&22815): the deletion machinery these endpoints invoke.
- Closed-beta deletion scope: whether closed beta ships soft deletion or permanent delete only is still open (discussion); it decides these endpoints' semantics.
Out of scope
Quarantine, now tracked in S17: artifact quarantine endpoints (#482) • Unassigned. ADR-009 defines it as a per-artifact PATCH, not a bulk route, so the bulk surface above is unaffected.
This phase patches the S17 spec and follows the repo gate: spec MR, plan MR, implementation. Part of &22341.
Workstream status (2026-08-20)
The graph is a ledger of work in progress and work to be done: a step's node leaves the graph when its merge request merges, and the Merge request status table below keeps the full step-to-MR record, merged rows included. Reading the colors, green nodes have an open merge request and link to it, amber nodes are being implemented but their merge requests have not opened yet, and grey nodes are planned. Edges are the plan's dependency graph among the remaining nodes, so every edge shown is an unsatisfied dependency. Blocking follow-ups join the map when they are filed and carry no plan edges. A follow-up that has no merge request yet stays grey and links to its tracking issue.
Dependency graph
graph TD
S38["Step 38: S22 accounting emit (!1754)"]
FU764["Follow-up: blob_sha256 delete-probe indexes (#764)"]
click S38 "https://gitlab.com/gitlab-org/ops/artifact-registry/-/merge_requests/1754"
click FU764 "https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/764"
classDef stOpen fill:#c8e6c9,stroke:#2e7d32,color:#1b5e20
classDef stInBuild fill:#ffecb3,stroke:#ff8f00,color:#ff6f00
classDef stPlanned fill:#f5f5f5,stroke:#9e9e9e,color:#424242
class S38 stOpen
class FU764 stPlannedMerge request status
type::feature — it describes new API endpoints (artifact write/delete operations) being added to the Artifact Registry management API, which is new functionality rather than a bug fix or maintenance task.
The following labels are confirmed present:
type::featureCategory:Artifact Registrydevops::packagegroup::package registry
If this classification doesn't look right to you, please feel free to update the labels and leave a comment explaining the change. Thanks!