Remove migration_state in ContainerRepository GraphQL

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Deprecation Summary

The migrationState field in the ContainerRepositoryType GraphQL API is being removed as part of API cleanup efforts. This field is being deprecated to streamline and improve the API structure.

Documentation

• Deprecation notice: #459869
• Implementation MR: !151442 (merged)
• Related issue: #409873 (closed)

Product Usage

This deprecation is part of API cleanup efforts to remove unused or unnecessary fields. The migrationState field in ContainerRepositoryType is being removed to improve API maintainability and clarity.

Breaking Change?

Yes - This deprecation contains a breaking change as it removes a field from the GraphQL API.

Affected Customers

Who is affected by this deprecation:

• GitLab.com
• Self-managed
• Dedicated

What pricing tiers are impacted:

• GitLab Free
• GitLab Premium
• GitLab Ultimate

[x] Internal note outlining details of customer impact has been created

Deprecation Milestone

• Announcement: GitLab 17.6
• Removal: GitLab 18.0

Planned Removal Milestone

The feature / functionality will be removed in milestone: 18.0

Links

• Issue: #459869
• Implementation MR: !151442 (merged)
• Related Issue: #409873 (closed)

Rollout Plan

DRI Engineers: [To be assigned] DRI Engineering Manager: [To be assigned]

Migration Steps:

1. Identify GraphQL queries using migrationState
2. Remove references to the field
3. Update application logic that depends on this field
4. Test updated queries

Impact Assessment

• Severity: Low
• Scope: Project
• Resolution role: Developer
• Manual task required: Yes
• Implementation window: 3 months

Development Tasks

• Deprecate migrationState field
• Update GraphQL schema documentation
• Create migration examples
• Add deprecation warnings
• Remove field in 18.0

Communication Plan

DRI Product Manager: [To be assigned]

Internal Communication

• Create internal note for customer-facing teams
• Update API documentation
• Prepare support guide

External Communication

• Announce deprecation in 17.6
• Update GraphQL documentation
• Create migration guide
• Send reminders before 18.0 release

Labels