Loading
Draft: [skip ci] Remove the ciStageUpdated subscription
What does this MR do and why?
Removes the ciStageUpdated subscription, its trigger on Ci::Build and Subscriptions::Ci::Stages::JobsUpdated.
- Its only consumer, the stage dropdown of the pipeline mini graph, moves to
ciStageJobsUpdatedin !266647. - The trigger publishes one Redis message for every job transition, whether or not anyone listens. On GitLab.com that is about 750 messages each second (Grafana,
action_cable_broadcasts_total{broadcasting="graphql-event:ciStageUpdated"}, 2026-10-21), while browsers received about 13 updates each second. - The field is an experiment, so it can go without a deprecation.
When to merge
After !266647 is deployed. Browser tabs that were opened before that deploy still subscribe to ciStageUpdated. Once this MR is deployed, those tabs stop getting live updates in the stage dropdown until they reload. Their subscription request then fails validation, which can show as an error in the browser console.
How to set up and validate locally
bin/rspec spec/graphql/types/subscription_type_spec.rb spec/graphql/graphql_triggers_spec.rbMR acceptance checklist
Evaluate this MR against the MR acceptance checklist.
References
- Part of https://gitlab.com/gitlab-org/gitlab/-/work_items/630854, step C3
- Depends on !266647, which moves the last consumer
- Replacement subscription: !266649
- Rollout of
ciStageUpdated, closed over cardinality concerns: #581569 (closed)
Edited by Miguel Rincon