Sync routes snapshot: add the merge request cancel_auto_merge API route

José M. Requena Plensrequested to merge
jmrp/http-router:sync-cancel-auto-merge-route into main

What does this MR do and why?

Refreshes test/routes/gitlab_routes.json and test/routes/__snapshots__/routes.spec.ts.snap to include the route added by gitlab-org/gitlab!255702:

/api/:version/projects/:id/merge_requests/:merge_request_iid/cancel_auto_merge

It matches the existing /api/v4/projects/:PROJECT_ID_OR_ROUTE/* rule and claims the project, the same as cancel_merge_when_pipeline_succeeds beside it, so src/routes.ts and src/generated_route_guards.ts do not change. It is an authenticated API route, which is the case docs/adding-gitlab-routes.md says needs only a refreshed snapshot.

The download also carries a rename that is already on gitlab-org/gitlab master: /api/:version/projects/:id/jobs/:job_id/runtime_environment_key became /api/:version/jobs/:id/runtime_environment_key, and the source branch was rebuilt on current master before the snapshot was pulled. !1351 (merged) carries the same rename, so the two agree on it whichever merges first.

On timing: gitlab-org/gitlab!255702 is still in review. Once this merges, a GitLab merge request that changes config/routing/gitlab_routes.json without carrying this route will report it as router-only drift until gitlab-org/gitlab!255702 merges, so you may prefer to merge this close to that one.

References

Related to gitlab-org/gitlab!255702

How to set up and validate locally

  1. GITLAB_ROUTES_PROJECT=gitlab-community/gitlab-org/gitlab npm run download-gitlab-routes -- jmrp-mr-cancel-auto-merge
  2. npm run generate-route-guards, which changes nothing.
  3. npm run test -- routes.spec.ts, then -u after reading the new rows.
  4. npm test.

MR acceptance checklist

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

Merge request reports