Commit 8730382f authored by Max Woolf's avatar Max Woolf 3️⃣
Browse files

Update API Platform team roadmap for FY27-Q3

parent 7944edcf
Loading
Loading
Loading
Loading
+35 −12
Changes for content/handbook/engineering/infrastructure-platforms/developer-experience/api/_index.md: 35 added lines, 12 removed lines.
Original line number Diff line number Diff line
@@ -53,29 +53,52 @@ As a lean team, we balance high confidence in our "Now" commitments while keepin

### Now

**Focus: Documentation - API strategy and discoverability, Platform Health** (FY27-Q2)
**Focus: Documentation and Development - One API model for modular features** (FY27-Q3)

- [REST API Docs Production Readiness and GA Launch](https://gitlab.com/groups/gitlab-org/quality/-/work_items/402)
- [Upgrade Grape from 2.0.0 to 2.4.x](https://gitlab.com/groups/gitlab-org/quality/-/work_items/385)
- [REST API Docs Production Readiness and Public Beta Launch](https://gitlab.com/groups/gitlab-org/quality/-/work_items/402)
- [REST API Docs GA: retire the Markdown reference](https://gitlab.com/groups/gitlab-org/quality/-/work_items/471)
- [OpenAPI Annotations - REST Endpoint Tier](https://gitlab.com/groups/gitlab-org/quality/-/work_items/366)
- [Establish one API definition model for all GitLab modular features](https://gitlab.com/groups/gitlab-org/quality/-/work_items/465)
- [Ship an API spec with every new modular feature by default](https://gitlab.com/groups/gitlab-org/quality/-/work_items/429)
- [Make every modular feature API state how to authenticate against it](https://gitlab.com/groups/gitlab-org/quality/-/work_items/466)

For more information on current projects, refer to our [top-level epic](https://gitlab.com/groups/gitlab-org/quality/-/epics/218).
For the full list of current, ready, and completed work, refer to our [parent epic](https://gitlab.com/groups/gitlab-org/quality/-/work_items/200).

### Next

**Focus: Data-driven - Build trust and visibility** (FY27-Q3)
**Focus: Deprecations and Data-driven - GraphQL quality and API visibility per team** (FY27-Q4)

- Establish lifecycle management policies for GraphQL endpoints
- Improve API observability and monitoring capabilities for GraphQL API
- Build visibility into API usage patterns and customer needs for REST and GraphQL APIs
- **GraphQL schema lifecycle**: remove deprecated fields on schedule ahead of GitLab 20.0, graduate experiments, and block breaking schema changes in CI.
- **GraphQL N+1 and query cost**: make efficient data loading the default and catch N+1 queries before merge.
- **GraphQL schema consistency**: lint new schema additions in CI and define one error model.
- **API scorecard per team**: one view per stage group of the quality of the REST and GraphQL APIs it owns.
- [Add GraphQL support to Scalar, upstream](https://gitlab.com/groups/gitlab-org/quality/-/work_items/439)

### Later

**Focus: Development - Enable API-first by default** (FY27-Q3 and beyond)
**Focus: Development - Safe, consistent APIs across GitLab components** (FY28 and beyond)

- [OpenAPI Annotations - REST Parameters](https://gitlab.com/groups/gitlab-org/quality/-/work_items/474)
- [Block breaking API changes in CI across all GitLab components](https://gitlab.com/groups/gitlab-org/quality/-/work_items/432)
- [Provide a contract testing framework for GitLab APIs](https://gitlab.com/groups/gitlab-org/quality/-/work_items/434)
- [Reduce reactive API security work with pre-Rails request validation](https://gitlab.com/groups/gitlab-org/quality/-/work_items/430)
- [Own and deliver the shared GitLab protobuf monorepo](https://gitlab.com/groups/gitlab-org/quality/-/work_items/431)
- [Upgrade GitLab monolith Rest API framework (Grape) from 3.2 to 4.0](https://gitlab.com/groups/gitlab-org/quality/-/work_items/473)
- [Improve API-first development adoption](https://gitlab.com/groups/gitlab-org/quality/-/work_items/383)

### Recently delivered

- Create tooling that makes API development efficient for REST and GraphQL APIs
- Explore architectural improvements for parity and consistency across REST and GraphQL APIs
- Enable teams to self-serve their entire API needs from development to deprecation
Since the last roadmap update in May 2026, we delivered:

- [Support all Grape keywords](https://gitlab.com/groups/gitlab-org/quality/-/work_items/321)
- [REST API Docs Internal Beta Launch](https://gitlab.com/groups/gitlab-org/quality/-/work_items/369)
- [Burn down Redocly OpenAPI 3.0 specification errors and warnings](https://gitlab.com/groups/gitlab-org/quality/-/work_items/363)
- [Upgrade Grape from 2.0.0 to 2.4.x](https://gitlab.com/groups/gitlab-org/quality/-/work_items/385)
- [Improve detection of canary-breaking GraphQL frontend and backend changes](https://gitlab.com/groups/gitlab-org/quality/-/work_items/436)
- [Prevent REST Entity Exposure Growth](https://gitlab.com/groups/gitlab-org/-/work_items/20829)
- [Render multiple API specs in the interactive reference](https://gitlab.com/groups/gitlab-org/quality/-/work_items/433)
- [Upgrade GitLab monolith Rest API framework (Grape) from 2.4.0 to 3.2.1](https://gitlab.com/groups/gitlab-org/quality/-/work_items/438)
- [Publish Orbit and Artifact Registry REST APIs in the public API reference](https://gitlab.com/groups/gitlab-org/quality/-/work_items/428)

### Keeping The Lights On (KTLO)