Deprecation issue: CodeClimate-based Code Quality scanning will be removed

Understanding this change

Does this change impact you?

The steps for users on a SaaS platform (GitLab.com, GitLab Dedicated) and for self-managed to check whether they will be impacted are:

1. Browse to the project you want to check
2. Check the GitLab CI/CD configuration files (e.g. .gitlab-ci.yml)
3. If the Code-Quality.gitlab-ci.yaml template is included, the project is impacted

The Advanced Search Deprecations tool can be used to check for the impact of this change. If the output mentions CodeClimate-based Code Quality scanning will be removed in a row, the project in that particular finding is impacted.

What does impact from this change look like?

If you are impacted by this change, you will notice that the Code-Quality.gitlab-ci.yml CI/CD template no longer executes scans. You might notice errors if other [need] (https://docs.gitlab.com/ci/yaml/#needs) or depend on the CodeClimate-based Code Quality scanning that this template used to execute.

We won't delete previously published container images or remove the ability to run them by using custom CI/CD pipeline job definitions.

⚠️ On GitLab.com, this will occur during window 1 (April 21 - 23, 2025 from 09:00 UTC to 22:00 UTC) – before the release of GitLab 18.0.

📅 This change has been postponed to %19.0

How to prepare for this change?

The steps for users on a SaaS platform (GitLab.com, GitLab Dedicated) and for self-managed to prepare for this change are:

1. Remove the Code-Quality.gitlab-ci.yml CI/CD template from your GitLab CI/CD configuration

To replace the functionality provided by including the Code-Quality.gitlab-ci.yml CI/CD template, you can optionally:

1. Choose another tool to integrate with Code Quality
2. Integrate the tool into your CI/CD pipeline
3. Import the results generated by the tool you chose as a codequality report artifact

We maintain a list of common tools with Code Quality that you can choose from.

---

GitLab customers with an active subscriptions can reach out to GitLab Support when encountering problems with the guidance above.

---

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

You can learn more about upcoming changes in the Deprecations and removals by version and Breaking change deployments on GitLab.com docs.

Deprecation Summary

Note: This is a copy of the deprecation notice that is published in documentation.

In GitLab 19.0, we will remove CodeClimate-based Code Quality scanning. In its place, you should use quality tools directly in your CI/CD pipeline and provide the tool's report as an artifact. Many tools already support the required report format, and you can integrate them by following the documented steps.

We expect to implement this change by:

1. Changing the Code-Quality.gitlab-ci.yml CI/CD template to no longer execute scans. Today, this template runs CodeClimate-based scans. (We plan to change the template rather than delete it to reduce the impact on any pipelines that still include the template after 19.0.)
2. No longer running CodeClimate-based scanning as part of Auto DevOps.

Effective immediately, CodeClimate-based scanning will receive only limited updates. After End of Support in GitLab 19.0, we won't provide further updates. However, we won't delete previously published container images or remove the ability to run them by using custom CI/CD pipeline job definitions.

For more details, see Scan code for quality violations.

Breaking Change

Yes.

Action required

For more details, see Scan code for quality violations.

Affected Topology

All deployment types

Affected Tier

All tiers

Deprecation Milestone

%17.2

Planned Removal Milestone

%19.0

Links

Checklists

Click to expand

Labels

• This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
• This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

~~Window 1

This window takes place on April 21 - 23, 2025 from 09:00 UTC to 22:00 UTC.~~

Please add links to the relevant merge requests.

• As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page.
    • See MR: Docs: Deprecate CodeClimate-based quality scanning (!158840 - merged) • Connor Gilbert, Amar Patel+ • 17.3
  • Documentation has been updated to mark the feature as deprecated.
• On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • Note: this page no longer exists
• On the major milestone:
  • The deprecated item has been removed.
  • If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.

Mentions

• Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
  • To see who the stable counterparts are for a product team visit product categories
    • If there is no stable counterpart listed for Sales/CS please mention @timtams
    • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
    • If there is no stable counterpart listed for Marketing please mention @cfoster3
• Your GPM has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.