Skip to content

Remove workspace termination fields from client side code

Issue: GraphQL cleanup on rails backend and frontend (#509788 - closed)

What does this MR do and why?

As part of an ongoing deprecation process in the linked issue, we would need to get rid of the client-side code that depends on the already deprecated fields in GraphQL.

There is no drop in replacement and no expected change in functionality. There is also no visible UI change as the components that provided access to the removed functionality were taken out of the UI in an earlier MR.

The fields are still served by the backend but will be removed in the next milestone, in line with:

https://docs.gitlab.com/development/graphql_guide/reviewing/#multiversion-compatibility

References

#509788 (closed)

Screenshots or screen recordings

Screenshot_2025-04-10_at_6.37.20_AM

How to set up and validate locally

Creating a workspace Via the UI should be successful.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Safwan Ahmed

Merge request reports

Loading