Remove unused dependency_bump_run_command feature flag

Hitesh Raghuvanshirequested to merge
613911-remove-dependency-bump-run-command-ff into master

What does this MR do and why?

This MR removes the dependency_bump_run_command feature flag, a beta-type flag (default disabled, milestone 19.3, group::compliance) introduced in !250168 (merged). Its only function was to push a header to the AI Gateway; GitLab itself never called Feature.enabled? on it. On AI Gateway main, nothing reads this flag — run_command is already listed unconditionally in the resolve_dependency_bump flow's toolset config, and the only code that ever consumed the flag lives on an unmerged, explicitly "reference, do not merge" draft MR. With no consumer on either side, this is a no-op cleanup.

Changes:

  • Deleted ee/config/feature_flags/beta/dependency_bump_run_command.yml
  • Removed the Gitlab::AiGateway.push_feature_flag(:dependency_bump_run_command, current_user) call from ee/lib/api/helpers/duo_workflow_helpers.rb
  • Removed the matching it 'pushes dependency_bump_run_command feature flag' example from ee/spec/lib/api/helpers/duo_workflow_helpers_spec.rb

References

Screenshots or screen recordings

Not applicable — this removes an unused feature flag and its plumbing, with no UI change.

How to set up and validate locally

  1. Run the affected spec: bundle exec rspec ee/spec/lib/api/helpers/duo_workflow_helpers_spec.rb. Result: 23 examples, 0 failures.
  2. Run Rubocop against the two changed Ruby files (ee/lib/api/helpers/duo_workflow_helpers.rb and ee/spec/lib/api/helpers/duo_workflow_helpers_spec.rb). Result: no offenses.

MR acceptance checklist

This MR meets the MR acceptance checklist. A few notes specific to this change:

  • EE-only change — no CE-side files touched.
  • No database migration involved.
  • No docs update needed — this was a default-off beta flag with no documented user-facing behavior.

🤖 Generated with Claude Code

Merge request reports