This epic is the SSOT for ongoing and planned API Platform group work. Please find below the work that is currently in-progress. ## Hours Worked | Epic | Category | DRI | Total Hours | |------|----------|-----|-------------| | [API Platform - Business As Usual](https://gitlab.com/groups/gitlab-org/quality/-/epics/231) | ~"infra-category::KTLO" | @mwoolf | 0.0 | | [API - Security bug fixes](https://gitlab.com/groups/gitlab-org/quality/-/epics/260) | ~"infra-category::Tech Debt" | @pjphillips | 0.0 | | [REST API Docs GA: retire the Markdown reference](https://gitlab.com/groups/gitlab-org/quality/-/epics/471) | ~"infra-category::Tech Debt" | @idurham | 0.0 | | [Establish one API definition model for all GitLab modular features](https://gitlab.com/groups/gitlab-org/quality/-/epics/465) | ~"infra-category::Internal Innovation" | @mwoolf @vwolanyk | 0.0 | | [REST API Docs Production Readiness and Public Beta Launch](https://gitlab.com/groups/gitlab-org/quality/-/epics/402) | ~"infra-category::Customer Innovation" | @cfeick | 0.0 | | [OpenAPI Annotations - REST Endpoint Tier](https://gitlab.com/groups/gitlab-org/quality/-/epics/366) | ~"infra-category::Customer Innovation" | @vwolanyk | 0.0 | ## Project Work ### :hourglass: Work In Progress These epics are currently in progress | **Topic** | **Start Date** | **Target End Date** | **Summary** | |-----------|----------------|---------------------|-------------| | [API Platform - Business As Usual](https://gitlab.com/groups/gitlab-org/quality/-/epics/231) <br/> @mwoolf (+0 participants) <br/> ~"group::api platform" | 2025-08-04 | 2026-07-31 | **2026-07-16**: <br>:clock1: **total hours spent this week by all contributors: 22**<br><br>:tada: **achievements**:<br><br>* Made some improvements to the quality of the generated OpenAPI 3.0 specification: https://gitlab.com/gitlab-org/gitlab/-/work_items/593537. These required a small breaking change to fix a latent bug: https://gitlab.com/gitlab-com/Product/-/work_items/14561<br>* Made some improvements to the enforcement of rules that prevent unlimited growth of API responses: https://gitlab.com/gitlab-org/gitlab/-/work_items/605460<br><br> | | [API - Security bug fixes](https://gitlab.com/groups/gitlab-org/quality/-/epics/260) <br/> @pjphillips (+0 participants) <br/> ~"group::api platform" | 2025-09-01 | 2026-07-01 | **2026-05-28**: <br>:clock1: **total hours spent this week by all contributors**: 5h<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/260#note_3392208106_<br><!-- STATUS NOTE END --><br><br/><br/>**Nested Epics: 1**<br/><br/>• https://gitlab.com/groups/gitlab-org/quality/-/epics/314+ <br/> | | [REST API Docs GA: retire the Markdown reference](https://gitlab.com/groups/gitlab-org/quality/-/epics/471) <br/> @idurham (+0 participants) <br/> ~"group::api platform" | | | | | [Establish one API definition model for all GitLab modular features](https://gitlab.com/groups/gitlab-org/quality/-/epics/465) <br/> @mwoolf @vwolanyk (+0 participants) <br/> ~"group::api platform" | | 2026-10-23 | **2026-10-08**: <br>:tada: **achievements**:<br><br>- Initial ADR was merged: https://gitlab.com/gitlab-org/gitlab/-/work_items/624041<br>- Follow-up with quality bar for OpenAPI specs was also merged: https://gitlab.com/gitlab-org/gitlab/-/work_items/624043<br><br>:issue-blocked: **blockers**:<br><br>:arrow_forward: **next**:<br><br>- Publish the ruleset as a versioned file, plus the CI component that runs it. (https://gitlab.com/gitlab-org/gitlab/-/work_items/624044)<br>- Pick up the remaining issues.<br><br><br>Currently on track, next week will be pivotal to ensure completion before end of October.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/465#note_3974266361_<br><!-- STATUS NOTE END --><br> | | [REST API Docs Production Readiness and Public Beta Launch](https://gitlab.com/groups/gitlab-org/quality/-/epics/402) <br/> @cfeick (+3 participants) <br/> ~"group::api platform" | | 2026-10-30 | **2026-09-17**: <br>Everything the team can do has been done! Now only the work from the Technical Writing team remains.<br><br>:tada: **achievements**:<br><br>* The Technical Writing team is organizing 50+ MRs that bring over to GitLab's OpenAPI specification the information on ~2000 parameters and routes that is currently sitting in docs<br><br>:issue-blocked: **blockers**:<br><br>*<br><br>:arrow_forward: **next**:<br><br>* Open the MRs, complete the review process for them and get them merged<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/402#note_3846633242_<br><!-- STATUS NOTE END --><br> | | [OpenAPI Annotations - REST Endpoint Tier](https://gitlab.com/groups/gitlab-org/quality/-/epics/366) <br/> @vwolanyk (+0 participants) <br/> ~"group::api platform" | | 2026-10-30 | **2026-10-01**: <br><!-- Create a high level summary (optional but encouraged) --><br><br>:clock1: **total hours spent this week by all contributors**: 15<br><br>:status: **TL;DR**: [one line summary of the status of the epic eg. why is date changed, why is epic at risk]<br><br>:tada: **achievements**:<br><br>- Custom component built and merged<br>- spec generation now includes tier<br><br>:issue-blocked: **blockers**:<br><br>- the last issue is currently blocked as there is inconsistency around `rout_setting` definitions<br><br>:arrow_forward: **next**:<br><br>- decide on whether to include endpoint tier info on GA release and how to backfill tiers<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/366#note_3934204750_<br><!-- STATUS NOTE END --><br> | ### :soon: Ready Linked epics that are ready to start | **Topic** | |-----------| | [Upgrade GitLab monolith Rest API framework (Grape) from 3.2 to 4.0](https://gitlab.com/groups/gitlab-org/quality/-/epics/473) <br/> ~"group::api platform" | | [Ship an API spec with every new modular feature by default](https://gitlab.com/groups/gitlab-org/quality/-/epics/429) <br/> ~"group::api platform" | | [Add GraphQL support to Scalar, upstream](https://gitlab.com/groups/gitlab-org/quality/-/epics/439) <br/> ~"group::api platform" | | [Block breaking API changes in CI across all GitLab components](https://gitlab.com/groups/gitlab-org/quality/-/epics/432) <br/> ~"group::api platform" | | [Reduce reactive API security work with pre-Rails request validation](https://gitlab.com/groups/gitlab-org/quality/-/epics/430) <br/> ~"group::api platform" | ### :arrow_forward: Next These are the epics we will be focusing on next | **Topic** | **Target Start Date** | **Summary** | |-----------|-----------------------|-------------| | [Make every modular feature API state how to authenticate against it](https://gitlab.com/groups/gitlab-org/quality/-/epics/466) <br/> (+0 participants) <br/> ~"group::api platform" | | | | [Own and deliver the shared GitLab protobuf monorepo](https://gitlab.com/groups/gitlab-org/quality/-/epics/431) <br/> (+0 participants) <br/> ~"group::api platform" | | | | [Provide a contract testing framework for GitLab APIs](https://gitlab.com/groups/gitlab-org/quality/-/epics/434) <br/> (+0 participants) <br/> ~"group::api platform" | | | | [Improve API-first development adoption](https://gitlab.com/groups/gitlab-org/quality/-/epics/383) <br/> (+0 participants) <br/> ~"group::api platform" | | | ### :stop_button: Triage Epics that are currently being triaged | **Topic** | **Summary** | |-----------|-------------| | [Enable API-First Development Through Enhanced Training and Documentation](https://gitlab.com/groups/gitlab-org/quality/-/epics/270) <br/> ~"group::api platform" | | | [Make OpenAPI 3.0 REST SSoT](https://gitlab.com/groups/gitlab-org/quality/-/epics/287) <br/> ~"group::api platform" | | ### :white_check_mark: Completed Work Items that have been completed <details> | **Topic** | **Started** | **Ended** | **Summary** | |-----------| ------------| ----------| ------------ | | [Create API team roadmap](https://gitlab.com/groups/gitlab-org/quality/-/epics/203) <br/> ~"group::api platform" | 2025-08-18 | 2025-09-24 | **2025-09-17**: <br>Max and Chance presented the team and our roadmap at the Engineering All Hands, so I think we can consider this epic fully complete :tada:<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/203#note_2756017387_<br><!-- STATUS NOTE END --><br> | | [REST API Style Enforcement for the benefit of OpenAPI enforcement](https://gitlab.com/groups/gitlab-org/quality/-/epics/233) <br/> ~"group::api platform" | 2025-09-13 | 2026-01-09 | **2026-01-07**: <br>:clock1: **total hours spent this week by all contributors**: 0<br><br>:tada: **achievements**:<br><br>* See [closing statement](https://gitlab.com/groups/gitlab-org/quality/-/epics/233#note_2984959726)<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/233#note_2987487672_<br><!-- STATUS NOTE END --><br> | | [Implement OpenAPI 3.0 Spec Generation](https://gitlab.com/groups/gitlab-org/quality/-/epics/232) <br/> ~"group::api platform" | 2025-10-11 | 2025-11-21 | **2025-11-20**: <br>:tada: **achievements**:<br><br>This Epic can be closed, please see the [closing statement](https://gitlab.com/groups/gitlab-org/quality/-/epics/232#closing-statement)<br><br><!--STATUS NOTE END--><br> | | [GraphQL Metadata Enforcement Initiative](https://gitlab.com/groups/gitlab-org/quality/-/epics/243) <br/> ~"group::api platform" | 2026-01-06 | 2026-01-26 | **2026-01-21**: <br>:clock1: **total hours spent this week by all contributors**: 18<br><br>:tada: **achievements**:<br><br>- @mwoolf wrote an uncharacteristically large amount of JavaScript this week. ([MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218657))<br>- Once this MR is merged, we can close this epic and allow feature teams to backfill their own feature categories.<br>- Filled in feature categories for the _most_ popular GraphQL queries.<br>- Announced changes to engineering week-in-review.<br><br>:issue-blocked: **blockers**:<br><br>- None.<br><br>:arrow_forward: **next**:<br><br>- @mwoolf responding to frontend maintainer comments on the above MR. Merge it. Close the epic :tada:<br><br>Update 2026-01-22:<br><br>Engineering work nearing a close. New linting rules are enforced in the GitLab monolith and announcements across engineering have been very well received.<br><br> | | [Prevent REST Entity Exposure Growth](https://gitlab.com/groups/gitlab-org/-/epics/20829) <br/> ~"group::api platform" | 2026-03-03 | 2026-08-07 | **2026-04-16**: <br>:clock1: **total hours spent this week by all contributors**: 0<br><br>The important but non-urgent remaining issue is a follow-up to the original scope of the epic, which due to other priorities I haven't had the chance to work on yet.<br><br>:tada: **achievements**:<br><br>*<br><br>:issue-blocked: **blockers**:<br><br>* Other priorities (security issues)<br><br>:arrow_forward: **next**:<br><br>*<br><br>_Copied from https://gitlab.com/groups/gitlab-org/-/epics/20829#note_3255438516_<br><!-- STATUS NOTE END --><br> | | [API Platform tooling survey - FY26Q1](https://gitlab.com/groups/gitlab-org/quality/-/epics/352) <br/> ~"group::api platform" | 2026-03-16 | 2026-04-14 | **2026-04-09**: <br>**Total contributor hours this week:** 5.5<br><br>**Closing status**<br><br>**Original problem:** The API Platform roadmap lacked quantitative data on the confidence of engineers building API-first in the Rails monolith.<br><br>**What we did:** We designed, distributed, and collected responses for a survey assessing the current state of API-first training, tools and engineer confidence/skills. The survey ran for a two-week collection period and responses have been analysed to produce actionable findings. A [new epic has been created](https://gitlab.com/groups/gitlab-org/quality/-/work_items/383) with concrete next steps.<br><br>:tada: **Achievements:**<br>- Survey designed and distributed to all of engineering, with 50 responses.<br>- Two-week response collection period completed successfully<br>- Survey results analysed and new epic created with next steps.<br><br>:chart_with_upwards_trend: **Impact:** The survey findings provide a data-driven foundation for prioritising API Platform tooling and training investments in upcoming quarters. Survey results can be [found above](https://gitlab.com/groups/gitlab-org/quality/-/work_items/352#note_3217691293).<br><br>:white_check_mark: This project is complete. Grand Reviewers, please close this epic.<br><br>Shout out to @ntepluhina and @amyphillips for helping write, review and facilitate the survey.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/352#note_3233703176_<br><!-- STATUS NOTE END --><br> | | [REST API Docs Internal Beta Launch](https://gitlab.com/groups/gitlab-org/quality/-/epics/369) <br/> ~"group::api platform" | 2026-03-30 | 2026-05-13 | **2026-05-07**: <br>:clock1: **total hours spent this week by all contributors**: 39<br><br>:tada: **achievements**:<br><br>- Project complete<br><br>**Closing Status**<br><br>**Original Problem**: GitLab's REST API documentation was served from manually maintained Markdown pages with no interactivity and no support for EE endpoints. The experimental deployment in [&261](https://gitlab.com/groups/gitlab-org/quality/-/work_items/261) validated the OpenAPI 3.0 + Scalar approach, but did not yet meet quality standards for a production-ready, publicly accessible deployment.<br><br>**Changes Made**: The team built a continuously deployed API documentation site on top of the foundation established in [&261](https://gitlab.com/groups/gitlab-org/quality/-/work_items/261). This included automating daily spec fetches from `gitlab-org/gitlab`, applying docs.gitlab.com branding with full theme and mobile parity, configuring the `api.gitlab.com/rest/` domain, enabling CORS for live API testing, adding a Beta status indicator with a link to the feedback issue, and establishing a testing strategy with unit and e2e coverage. The Internal Beta was announced to GitLab team members this week, and we are now actively collecting feedback.<br><br>**Impact**: Scalar is now live as GitLab's first continuously deployed, interactive REST API reference covering the full API surface area including EE endpoints. The deployment is secure, performant, and publicly accessible as an Internal Beta. Team members can explore the docs and share feedback in [api-docs#21](https://gitlab.com/gitlab-com/gl-infra/api-docs/-/work_items/21), while remaining work has been moved to [&402](https://gitlab.com/groups/gitlab-org/quality/-/work_items/402) for follow-up iterations.<br><br>**Demo**: https://api.gitlab.com/rest<br><br>Shout-out to `@mwoolf` `@abignotti` `@vwolanyk` for their contributions :rocket:<br><br>**Please close epic during grand review**<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/369#note_3322243469_<br><!-- STATUS NOTE END --><br> | | [Upgrade Grape from 2.0.0 to 2.4.x](https://gitlab.com/groups/gitlab-org/quality/-/epics/385) <br/> ~"group::api platform" | 2026-05-04 | 2026-08-07 | **2026-07-30**: <br>Upgrade has been merged \~24 hours ago. Monitoring in case of unforeseen problems, but for now everything is going well!<br><br>:tada: **achievements**:<br><br>* The monolith is now running with Grape 2.4!<br><br>:issue-blocked: **blockers**:<br><br>*<br><br>:arrow_forward: **next**:<br><br>* Cleanup the codebase (i.e., remove a couple of temporary things that were there to allow CI to pass both with Grape 2.0 and 2.4) and close the epic<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/385#note_3620707014_<br><br><!--STATUS NOTE END--><br> | | [Improve detection of canary-breaking GraphQL frontend and backend changes](https://gitlab.com/groups/gitlab-org/quality/-/epics/436) <br/> ~"group::api platform" | 2026-07-30 | 2026-08-07 | **2026-07-30**: <br>Just created the epic today and started working on the first issue.<br><br>:tada: **achievements**:<br><br>* Created [the first MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/247826) that makes the warning in the Dangerbot comment more prominent!<br><br>:issue-blocked: **blockers**:<br><br>*<br><br>:arrow_forward: **next**:<br><br>* Merge the MR that has just been opened and start working on another child issue, depending on other priorities.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/436#note_3623405900_<br><!-- STATUS NOTE END --><br> | | [Upgrade GitLab monolith Rest API framework (Grape) from 2.4.0 to 3.2.1](https://gitlab.com/groups/gitlab-org/quality/-/epics/438) <br/> ~"group::api platform" | 2026-08-03 | 2026-10-06 | **2026-10-01**: <br>The upgrade has been merged and is now live in production!<br><br>:clock1: **total hours spent this week by all contributors**: 4<br><br>:status: **TL;DR**: If nothing unforeseen comes up, I'll be able to close this in the week of Oct 5th<br><br>:tada: **achievements**:<br><br>* The upgrade has been merged and is now live in production! Monitoring for any unforeseen problems<br><br>:issue-blocked: **blockers**:<br><br>* Not a blocker, but I'll be waiting until next week (starting on Oct 5th) to proceed with the remaining Epic activities (cleanup + announcement) to allow reacting more easily to any unforeseen problem that comes up in production<br><br>:arrow_forward: **next**:<br><br>* Be ready to react to any unforeseen issues in production, cleanup, announce the change<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/438#note_3934204280_<br><!-- STATUS NOTE END --><br> | | [Render multiple API specs in the interactive reference](https://gitlab.com/groups/gitlab-org/quality/-/epics/433) <br/> ~"group::api platform" | 2026-08-17 | 2026-10-01 | **2026-10-01**: <br>Work on this epic has been completed, closing it off!<br><br>:clock1: **total hours spent this week by all contributors**: 4<br><br>:status: **TL;DR**: Epic is closed.<br><br>:tada: **achievements**:<br><br>* The API reference site ([api.gitlab.com/rest/](https://api.gitlab.com/rest/)) can now show more than one API spec, and now shows 2 (GitLab's and Artifact Central's)! This can be easily done by just adding a single config entry<br><br>:issue-blocked: **blockers**:<br><br>*<br><br>:arrow_forward: **next**:<br><br>*<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/433#note_3934204430_<br><!-- STATUS NOTE END --><br> | | [Introduce Lifecycle Status to REST API](https://gitlab.com/groups/gitlab-org/quality/-/epics/316) <br/> ~"group::api platform" | | 2026-04-23 | **2026-04-16**: <br>:clock1: **total hours spent this week by all contributors**: 3h<br><br> | | [Deploy experimental documentation for OpenAPI v3.0 specification](https://gitlab.com/groups/gitlab-org/quality/-/epics/261) <br/> ~"group::api platform" | 2025-11-15 | 2026-03-19 | **2026-03-12**: <br>:clock1: **total hours spent this week by all contributors**: 4<br><br>:tada: **achievements**:<br><br>- Project complete<br><br>**Closing Status**<br><br>**Original Problem**: GitLab's REST API documentation was limited to manually maintained Markdown covering only a subset of the API. The incomplete OpenAPI 2.0 spec lacked EE endpoints and ability for interactivity, creating friction for customers, AI agents, and external teams trying to discover and build on GitLab's full API capabilities.<br><br>**Changes Made**:<br>- Generated a [valid OpenAPI 3.0](https://gitlab.com/groups/gitlab-org/quality/-/work_items/218) specification covering the entire REST API surface area, including EE endpoints<br>- Deployed an experimental API reference using open source tooling [Scalar](https://github.com/scalar/scalar)<br>- Established the [API Docs](https://gitlab.com/gitlab-com/gl-infra/api-docs) project for foundation<br><br>**Impact**: The full GitLab REST API is now discoverable and explorable through an experimental interactive reference for the first time. A complete, machine-readable OpenAPI 3.0 spec will unlock the ability to render API lifecycle status on all endpoints using end-to-end automation.<br><br>This experimental deployment validated adoption of OpenAPI and Scalar tooling for automated solution and provides the foundation for iterating on https://gitlab.com/groups/gitlab-org/quality/-/work_items/369+, which will continue next steps to complete branding styles, performance optimizations, and public launch preparation/comms.<br><br>**Demo**: https://api-docs-a0ae81.gitlab.io<br><br>Shout-out to `@mwoolf`, `@abignotti`, `@idurham`, `@kkloss` for their collaboration on this foundational work 🚀<br><br>---<br><br>**Please close this epic in the next Platforms Grand Review.**<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/261#note_3152601388_<br><!-- STATUS NOTE END --><br> | | [OpenAPI 3.0 Spec Bug Fixes/Polish required before Docs Launch](https://gitlab.com/groups/gitlab-org/quality/-/epics/285) <br/> ~"group::api platform" | 2025-11-19 | 2026-03-19 | **2026-03-12**: <br>Focused on closing out the remaining issues and wrapping up this epic.<br><br>:clock1: **total hours spent this week by all contributors**: 8<br><br>:tada: **achievements**:<br><br>* Closed the last 3 remaining issues:<br>* Closed [custom content types](https://gitlab.com/gitlab-org/gitlab/-/work_items/585182) and [missing param options](https://gitlab.com/gitlab-org/gitlab/-/work_items/591949), improving accuracy and consistency of the generated OpenAPI 3 specification<br>* Completed [OpenAPI 3.0 spec validation](https://gitlab.com/gitlab-org/gitlab/-/work_items/591007): the spec is now valid according to Swagger CLI. Added stricter Redocly CLI validation in `gitlab-com/gl-infra/api-docs` and created a [follow-up epic](https://gitlab.com/groups/gitlab-org/quality/-/work_items/363) to burn down the remaining Redocly errors. Swagger and Redocly are two different tools/platforms related to OpenAPI that also validate OpenAPI specifications, just in different ways<br>* The OpenAPI 3.0 specification is now valid and ready for the interactive docs launch<br><br>:issue-blocked: **blockers**:<br><br>* None<br><br>:arrow_forward: **next**:<br><br>* This epic is complete and ready to be closed in the next Grand Review<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/285#note_3152601440_<br><!-- STATUS NOTE END --><br> | | [Support all Grape keywords](https://gitlab.com/groups/gitlab-org/quality/-/epics/321) <br/> ~"group::api platform" | 2026-01-10 | 2026-05-08 | **2026-04-30**: <br>:clock1: **total hours spent this week by all contributors**: 1h<br><br>:tada: achievements:<br><br>* Shepherded the last 2 student community contributions for the last unsupported keywords (hhttps://gitlab.com/gitlab-org/gitlab/-/merge_requests/228360, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/228387)<br><br>:issue-blocked: blockers:<br><br>*<br><br>:arrow_forward: next:<br><br>* Grand Reviewers to close the epic!<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/321#note_3302583801_<br><!-- STATUS NOTE END --><br> | | [OpenAPI 3.0 Specification Generation and Validation](https://gitlab.com/groups/gitlab-org/quality/-/epics/284) <br/> ~"group::api platform" | 2026-01-12 | 2026-02-06 | **2026-02-04**: <br>:clock1: **total hours spent this week by all contributors**: 2<br><br>:tada: **achievements**:<br><br>* Completed the task! Added automated tooling (rake tasks ran in local linters and in CI jobs) in the GitLab project to trigger the generation and validation of the OpenAPI 3.0 specification<br><br>:issue-blocked: **blockers**:<br><br>*<br><br>:arrow_forward: **next**:<br><br>* Epic can be closed by our Grand Reviewers!<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/284#note_3056319803_<br><br><!--STATUS NOTE END--><br> | | [Burn down Redocly OpenAPI 3.0 specification errors and warnings](https://gitlab.com/groups/gitlab-org/quality/-/epics/363) <br/> ~"group::api platform" | 2026-03-12 | 2026-06-11 | **2026-05-28**: <br><br>:clock1: **total hours spent this week by all contributors**: 16 hours<br><br><br>:tada: **achievements**:<br><br>- @abignotti and @vwolanyk managed to burn down the last of the issues related to this epic<br>- there is only one last MR awaiting one more review and ready to merge before we can close the issue<br><br>:issue-blocked: **blockers**:<br><br>-<br><br>:arrow_forward: **next**:<br><br>- This epic should be closed within the next day or 2<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/363#note_3392208380_<br><!-- STATUS NOTE END --><br> | | [Publish Orbit and Artifact Registry REST APIs in the public API reference](https://gitlab.com/groups/gitlab-org/quality/-/epics/428) <br/> ~"group::api platform" | 2026-08-10 | 2026-10-06 | **2026-10-01**: <br>Work on this epic is basically done: both Artifact Central and Orbit API specs are now published in `api.gitlab.com/rest/`. Only one issue remains, which is an improvement on Orbit's spec. The 5 MRs from this issue are waiting for reviews.<br><br>:clock1: **total hours spent this week by all contributors**: 20<br><br>:status: **TL;DR**: One week left, if the reviews come in time we'll be able to make it<br><br>:tada: **achievements**:<br><br>* The Artifact Central spec is now live at [api.gitlab.com/rest/](https://api.gitlab.com/rest/#description/introduction/artifact-registry/artifact-central) and the old Pages website that published it does not show it anymore, so there is only one SSOT!<br>* The Orbit spec is now live at [api.gitlab.com/rest/](https://api.gitlab.com/rest/#description/introduction/artifact-registry/gitlab/tag/orbit)<br>* The 5 MRs that improve the information in Orbit's spec are in review<br><br>:issue-blocked: **blockers**:<br><br>*<br><br>:arrow_forward: **next**:<br><br>* Merge the remaining MRs and close the epic<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/428#note_3934204511_<br><!-- STATUS NOTE END --><br> | </details> ### :rotating_light: Epics that need attention These linked epics are not in the correct state or missing a workflow label <details> | **Topic** | **Links** | **Reason** | |-----------|-----------|-------------| | [OpenAPI 3](https://gitlab.com/groups/gitlab-org/quality/-/epics/218) <br/> (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | | [Establish API endpoint lifecycle policies](https://gitlab.com/groups/gitlab-org/quality/-/epics/269) <br/> (+0) <br/> group::api platform | Epic has ~"workflow-infra::Triage" but is closed | | [Rubocop Description Todos](https://gitlab.com/groups/gitlab-org/quality/-/epics/384) <br/> @vwolanyk (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | | [Use GraphQL complexity as the lever for DoS protection](https://gitlab.com/groups/gitlab-org/quality/-/epics/467) <br/> (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | | [GraphQL schema consistency: stricter cops, one error model, a shorter styleguide](https://gitlab.com/groups/gitlab-org/quality/-/epics/477) <br/> (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | | [GraphQL N+1 and query cost: batching, flat-query specs, and attribution by default](https://gitlab.com/groups/gitlab-org/quality/-/epics/476) <br/> (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | | [OpenAPI Annotations - REST Parameters](https://gitlab.com/groups/gitlab-org/quality/-/epics/474) <br/> (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | | [Fix GraphQL return type conflicts in GitLab's own queries](https://gitlab.com/groups/gitlab-org/quality/-/epics/470) <br/> (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | | [REST API Docs Post-GA Improvements](https://gitlab.com/groups/gitlab-org/quality/-/epics/414) <br/> (+0) <br/> group::api platform | Labeling problem, epic has no workflow label | </details>