<!--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> - [Collaborate/take over this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=611977) </details> <!--IssueSummary end--> <!--Title suggestion: [FF] `enable_dependency_bump_breaking_changes_pipeline_tracking` -- <short description>--> ## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/604832) currently behind the `enable_dependency_bump_breaking_changes_pipeline_tracking` feature flag. - DRI: @hraghuvanshi - Team Slack channel: `#g_sscs_compliance` > [!note] > > Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? <!--Optional but recommended: blast radius, data-loss risk, and the dashboard(s) you'll watch on https://dashboards.gitlab.net. Delete if not applicable.--> ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_sscs_compliance`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set enable_dependency_bump_breaking_changes_pipeline_tracking 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set enable_dependency_bump_breaking_changes_pipeline_tracking true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set enable_dependency_bump_breaking_changes_pipeline_tracking <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss enable_dependency_bump_breaking_changes_pipeline_tracking true /chatops gitlab run feature set --group=gitlab-org,gitlab-com enable_dependency_bump_breaking_changes_pipeline_tracking true /chatops gitlab run feature set --user=hraghuvanshi enable_dependency_bump_breaking_changes_pipeline_tracking true ``` ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/246152 19.3 /chatops gitlab run feature delete enable_dependency_bump_breaking_changes_pipeline_tracking --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set enable_dependency_bump_breaking_changes_pipeline_tracking false # production /chatops gitlab run feature set enable_dependency_bump_breaking_changes_pipeline_tracking false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete enable_dependency_bump_breaking_changes_pipeline_tracking --dev --pre --staging --staging-ref --production # remove entirely ``` <!--Uncomment the appropriate type label /label ~"type::feature" ~"feature::addition" /label ~"type::maintenance" /label ~"type::bug"-->