<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=510078) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=510078) </details> <!--IssueSummary end--> MR: Pending <!-- The first line of this issue description must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, 3. If there are multiple MRs: ``` MRs: - <MR 1 link with trailing +>` - <MR 2 link with trailing +>` - ... ``` 4. `MR: No MR` ...and the first description line of the MR should be `Issue: <Issue link with trailing +>` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#relationship-of-issues-to-mrs --> <!-- The following sections should be filled out as part of the refinement process before the issue is prioritized. For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#2-pre-iteration-planning-meeting --> ## Description We would need to remove the deprecated `devfile_ref` field from GraphQL `workspace_type` and mutation `WorkspaceOperations::Create`. Pls see the MR [here](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/171230) for reference. The field was deprecated in GitLab release %"17.8" as part of https://gitlab.com/gitlab-org/gitlab/-/merge_requests/171230+. Based on the deprecation process, https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/api/graphql/index.md#deprecation-and-removal-process. The earliest removal release would be %"19.0". ## Acceptance Criteria - [ ] Remove deprecated `devfile_ref` field from GraphQL `workspace_type` - [ ] Remove API doc references for this field <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/#-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->