## Artifact Registry Closed Beta — Defect Tracking This epic is the **single source of truth** for all bugs and defects discovered during the Artifact Registry Closed Beta. It is a child of [&21052 Artifact Registry Closed Beta](https://gitlab.com/groups/gitlab-org/-/epics/21052). --- ### 📍 Current Status (live) The views below are GLQL and render live. They are never stale; the triage log below records the judgment calls behind them. `~AR-Blocks::GA` means the fix gates the GA release and is worked during the beta, not postponed to it. ```glql display: table title: Fix before Closed Beta go-live (launch gate) fields: title, assignee, labels("priority::*") AS "Priority" limit: 20 sort: created asc query: group = "gitlab-org" AND state = opened AND label = "AR-Blocks::Closed-Beta" ``` ```glql display: table title: Fix before Closed Beta go-live, no owner fields: title, labels("priority::*") AS "Priority" limit: 20 sort: created asc query: group = "gitlab-org" AND state = opened AND label = "AR-Blocks::Closed-Beta" AND assignee = none ``` ```glql display: table title: Fix during Closed Beta (gates GA) collapsed: true fields: title, assignee, labels("priority::*") AS "Priority" limit: 50 query: group = "gitlab-org" AND state = opened AND label = "AR-Blocks::GA" ``` ### Triage log Dated record of triage decisions the live views cannot show. Newest first. - **2026-09-07 (correction)**: **Severity is retired entirely; there is no severity gate.** The earlier write-up of this decision (below) added a `~severity::1` "halt gate" and a "Halting Closed Beta" view, and stated that `~AR-Blocks::Closed-Beta` items are "work to finish during the beta". The scheme is two label families only. `~AR-Blocks::*` says which release the fix must precede (`~AR-Blocks::Closed-Beta` = fixed **before the first customer onboards**), `~priority::*` says in which order to start. The Halting view is removed and the gate reads off the "Fix before Closed Beta go-live" view: **CB launches when that list is empty**. In the same pass the blocker list was re-validated: every remaining blocker now opens with a highlighted `Closed Beta blocker: <category>` block justifying it (security, broken main path, must exist before the first customer); #1046 moved to GA, `registry-conformance#55` de-labeled (test-suite bug, not product), #1158 merged into #1025. `!2393` needs the same correction before it merges. - **2026-09-07**: **Severity retired from prioritization; `~priority::*` alone drives order.** Proposed by `@jdrpereira` and agreed by `@jaime`. The evidence: on the 16 open `~AR-Blocks::Closed-Beta` items, **8 of 8 `~priority::1` were S1-or-S2 and 6 of those 8 were S2**, so severity discriminated almost nothing once `~AR-Blocks::*` had been applied. Across all 58 children the spread was wider (S3 21, S2 20, S4 9, S1 2, none 7) — the collapse is specific to the Closed Beta queue, which is the queue anyone triaging actually reads. Changes: `~AR-Blocks::*` answers *which release*, `~priority::*` answers *what order*, both required. `~severity::2`/`::3`/`::4` are retired — not deleted from existing issues, but no longer added, routed on, or reported. **`~severity::1` survives as the CB halt gate only**, because "stop shipping until this closes" is the one statement priority cannot make; the epic's gate rule is unchanged and still reads off the `severity::1` search. Priority definitions are unchanged from 2026-09-03. The GLQL views, the statistics searches, the digest prompt, the required-labels list, and the `/bug-report` skill were all updated in the same pass. - **2026-09-03**: Full triage of all open items, with a per-item validation of every `~AR-Blocks::*` call. Everything now carries an `~AR-Blocks::*` label; Closed Beta blockers also carry an effort-based priority. Promoted to `~AR-Blocks::Closed-Beta`: [#1140](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1140), [#1131](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1131), [registry-conformance#55](https://gitlab.com/gitlab-org/ops/registry-conformance/-/issues/55), [#1134](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1134), [#1128](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1128), [#1133](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1133), [#1125](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1125), [#1083](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1083). Split from [#1025](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1025) (stays GA): [#1158](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/1158) measures the revoke-propagation window and documents the expectation for users. [ops#22](https://gitlab.com/groups/gitlab-org/ops/-/work_items/22) and the conformance-suite defects (#56–#59) confirmed GA. Priority now expresses start order by effort, not criticality: `priority::1` = missing implementation or cross-service work (start first, longer lead), `priority::2` = self-contained bug (quick). Severity unchanged. Top unowned blocker: [#417](https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/417). --- ### Blocking and priority policy Two labels decide everything, and **both are required on every bug**: | Label family | Answers | Values | |---|---|---| | `~AR-Blocks::*` | **Which release must this be fixed before?** | `Closed-Beta`, `GA`, `Self-Managed`, `Dedicated` | | `~priority::*` | **In what order do we start it?** | `priority::1`, `priority::2` | Priority expresses **start order by effort**, not criticality: | Label | Meaning | Why it is ordered this way | |---|---|---| | `~priority::1` | Missing implementation, or work that crosses into another service or team | Longer lead time, and often not ours to finish alone — **start first** | | `~priority::2` | Self-contained bug, fixable inside this codebase | Quick, and can be picked up any time capacity appears | **`~AR-Blocks::*` guide** — apply the label matching the earliest release the bug must be fixed before: | Label | When to use | |---|---| | `~AR-Blocks::Closed-Beta` | Must be fixed during Closed Beta for beta users to succeed | | `~AR-Blocks::GA` | Must ship before GA; does not affect beta users, or has a workaround they can live with | | `~AR-Blocks::Self-Managed` | Must be resolved before Self-Managed rollout | | `~AR-Blocks::Dedicated` | Must be resolved before Dedicated rollout | > **Work the Closed Beta queue in priority order.** `~AR-Blocks::Closed-Beta` sorted by `~priority::1` then `~priority::2` **is** the work order. There is no second axis to reconcile it against. #### Severity labels are retired, all of them No `~severity::*` label plays any role in this process, including `~severity::1`. Existing severity labels are harmless history: do not add new ones, do not route on them, and do not treat their absence as missing metadata. Any impact detail worth keeping goes in the report body, where a triager can read the actual claim instead of decoding a number. There is no severity-based halt gate. The launch gate is the blockers list itself (see `CB gate health` below). A defect that loses or exposes data, or takes the service down, is `~AR-Blocks::Closed-Beta` with `~priority::1`, escalated directly to the DRI and in Slack, not marked with a special label. ### 📊 Bug Statistics Live counts are in the Current Status views at the top. The searches below cover all AR bugs by the two labels the process routes on. Dated snapshots for week-over-week comparison live in comments on this epic, generated with the digest prompt below. | Search | What it answers | |---|---| | [Fix before Closed Beta go-live, all](https://gitlab.com/groups/gitlab-org/-/issues?label_name[]=type%3A%3Abug&label_name[]=AR-Blocks%3A%3AClosed-Beta&label_name[]=Category%3AArtifact%20Registry&state=opened) | **The launch gate.** Must be empty before the first customer onboards | | [Closed Beta blockers, `priority::1`](https://gitlab.com/groups/gitlab-org/-/issues?label_name[]=type%3A%3Abug&label_name[]=AR-Blocks%3A%3AClosed-Beta&label_name[]=priority%3A%3A1&label_name[]=Category%3AArtifact%20Registry&state=opened) | Start-first work: missing implementation or cross-service | | [Closed Beta blockers, `priority::2`](https://gitlab.com/groups/gitlab-org/-/issues?label_name[]=type%3A%3Abug&label_name[]=AR-Blocks%3A%3AClosed-Beta&label_name[]=priority%3A%3A2&label_name[]=Category%3AArtifact%20Registry&state=opened) | Self-contained, pick up any time | | [Closed Beta blockers with no owner](https://gitlab.com/groups/gitlab-org/-/issues?label_name[]=type%3A%3Abug&label_name[]=AR-Blocks%3A%3AClosed-Beta&label_name[]=Category%3AArtifact%20Registry&state=opened&assignee_id=None) | The queue that will not move | | [Fix during Closed Beta (gates GA)](https://gitlab.com/groups/gitlab-org/-/issues?label_name[]=type%3A%3Abug&label_name[]=AR-Blocks%3A%3AGA&label_name[]=Category%3AArtifact%20Registry&state=opened) | Worked during the beta; must close before GA | #### CB gate health The gate is a rule, not a stored value: **Closed Beta launches when the "Fix before Closed Beta go-live" view above is empty.** Read it from that link rather than from this page, which is only as fresh as its last edit. Every `~AR-Blocks::Closed-Beta` item must be fixed **before the first customer onboards**. Each blocker's description opens with a highlighted `Closed Beta blocker: <category>` block stating why it gates the launch, framed as the consequence for the user or the platform. An item whose justification stops holding loses the label; the label never outlives its justification. > [!warning] For agents and automation editing this epic > The labeling scheme is exactly two families: `~AR-Blocks::*` (which release the fix must precede) and `~priority::*` (start order). Do not introduce severity labels, severity-based views, halt gates, or any statement that `~AR-Blocks::Closed-Beta` work can be finished during the beta. Changes to the scheme itself require explicit sign-off from `@jdrpereira` and `@jaime`, recorded as a dated entry in the triage log. ### Snapshot Digest Prompt (Duo Chat / Claude) Paste this into Duo Chat or Claude to generate a dated snapshot comment: daily during bug bash week, weekly otherwise. The comments are the history trail; compare them day over day or week over week. ``` You are a release manager for the GitLab Artifact Registry team. Query the GitLab group `gitlab-org` for issues with labels `type::bug` AND `Category:Artifact Registry`. Filter on that, not on `artifact-registry::*`: the scoped stream label is required on product defects but not on every bug, so an `artifact-registry::*` filter silently drops the rest. Produce a digest with: - Open bugs broken down by `AR-Blocks::Closed-Beta` / `AR-Blocks::GA` / `AR-Blocks::Self-Managed` / `AR-Blocks::Dedicated` / no AR-Blocks label - Within `AR-Blocks::Closed-Beta`, split by `priority::1` and `priority::2`, and call out any carrying no priority label - Bugs opened and closed in the last 7 days, by AR-Blocks label - Any `AR-Blocks::Closed-Beta` bug open > 3 days without an assignee (flag as 🚨 UNOWNED BLOCKER) - A one-sentence CB gate summary: READY (no `AR-Blocks::Closed-Beta` open), NOT READY (count of open `AR-Blocks::Closed-Beta`) - A one-sentence CB progress summary: open `AR-Blocks::Closed-Beta` count, and the change since the previous snapshot Do not report or rank by any `severity::*` label. Severity is retired from the process; treat its presence as history and its absence as normal. Format as a Markdown table to paste as a comment on https://gitlab.com/groups/gitlab-org/-/work_items/23325 ``` --- ### Filing a Bug Run `/bug-report` in Claude Code from a checkout of [gitlab-org/ops/artifact-registry](https://gitlab.com/gitlab-org/ops/artifact-registry). The skill arrived with [!1802](https://gitlab.com/gitlab-org/ops/artifact-registry/-/merge_requests/1802), merged 2026-08-25, so the `main` links below resolve. The skill interviews for the evidence a report needs, decides the release gate and the priority against a rubric, resolves and validates the label set against the API, searches for duplicates, renders the body, shows it to you for confirmation, and files the issue as a child of this epic. `--dry-run` renders without filing. The skill is the source of truth for label selection, and this epic no longer carries its own label list. That is deliberate: the list this section used to hold named five labels that do not exist, and a prose list in an issue is checked by nobody, whereas [`ar-bug-labels`](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/.claude/skills/bug-report/scripts/ar-bug-labels) resolves every name against the API on each run and exits non-zero on one that is missing. Keeping one authority means a taxonomy change lands in one place. - Label taxonomy and target project: [`references/labels.md`](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/.claude/skills/bug-report/references/labels.md) - Release gate and priority: [`references/severity.md`](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/.claude/skills/bug-report/references/severity.md) - Report sections: [`references/template.md`](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/.claude/skills/bug-report/references/template.md) - Evidence to capture, and what to redact first: [`references/evidence.md`](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/.claude/skills/bug-report/references/evidence.md) Two things the skill will not decide for you: - **A security defect is filed confidential**, and the skill asks before filing anything with those characteristics. Auth bypass, cross-org data exposure, credential leak, and path traversal all qualify. A wrongly confidential issue costs a click; a wrongly public one cannot be undone. - **The assignee.** The skill suggests a DRI and leaves the issue unassigned. Triage owns assignment: within 24 hours for a security-class blocker, and within 72 hours for anything else `~AR-Blocks::Closed-Beta`. Without Claude Code, write the report by hand against [`references/template.md`](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/.claude/skills/bug-report/references/template.md) and take the labels from `references/labels.md`. Keep its section headings verbatim and in order. Nothing parses them — the digest above works off labels and dates, not the body — but a triager comparing reports reads the same section in the same place in each, and a missing answer shows up as an empty section instead of being inferred from a heading that was deleted. --- ### Required on Every Child Bug Issue Every bug filed as a child of this epic **must** have `~"type::bug"`, exactly one `~AR-Blocks::*`, exactly one `~priority::*`, `~"Category:Artifact Registry"`, one stream label, and `~"frontend"` or `~"backend"` where the fix lands in one of them. Format-specific defects also carry `~format::*` and `~repo-type::*`. **No `~severity::*` label is used.** Severity is retired entirely: do not add any severity label, and do not treat its absence as an incomplete report. `references/labels.md` above is the authoritative version of that list, including which stream labels exist and when each of these does not apply. Note that `~"type::frontend"` and `~"type::backend"` are **not** labels: the real ones are `~"frontend"` and `~"backend"`, and because `type::` is a scoped family, applying `~"type::backend"` silently evicts `~"type::bug"` and drops the issue out of every bug query.