<!--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> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=426324) </details> <!--IssueSummary end--> The `stage` argument stopped from being used in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/132320+, however deprecating and removing the argument from the PipelineWorker worker is challenging as the argument is in the middle of the argument list. One solution to remove the argument is also to deprecate the `entity_id` argument, which isn't necessary as we can get the `entity_id` from the `@pipeline_tracker`. So deprecating both arguments will allow us to deprecate both arguments `stage` and `entity_id` ### Proposed solution To deprecate and remove both arguments, we should follow the [Sidekiq development guidelines](https://docs.gitlab.com/ee/development/sidekiq/compatibility_across_updates.html#deprecate-and-remove-an-argument). And according to the guidelines we should create 3 MRs - MR1: Update PipelineWorker not to use the arguments and set a default value to them - MR2: Remove the arguments from PipelineWorker.perform_async. This MR should be deployed in a follow-up release - MR3: Remove the argument from the argument list. This MR should be deployed in a major release.