Deprecate security report schemas version 14-x-x

For guidance on the overall deprecations, removals and breaking changes workflow, please visit https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features

Deprecation Summary

As proposed and agreed in #361289 (closed), all security report schema versions before 15-0-0 are deprecated in GitLab %15.8.

Specifically, all schemas in https://gitlab.com/gitlab-org/gitlab/-/tree/master/ee/lib/ee/gitlab/ci/parsers/security/validators/schemas that match 14.\*.\* are deprecated in GitLab %15.8.

See Security report validation for more information.

Breaking Change

This is not a breaking change.

Please note that any security report scanner integration with GitLab using a deprecated schema version will result in a deprecation warning as a result of report validation.

Affected Topology

Affected Tier

• Ultimate

Checklists

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

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 entry has been created so the deprecation will appear in release posts and on the general deprecation page.
  • 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.
• 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.

Deprecation Milestone

%15.8

Planned Removal Milestone

%16.0

Links

Implementation plan

1. Add all 14.x.x versions to VERSIONS_TO_REMOVE_IN_16_0 in schema_validator.rb.

   1. ls -1 ./ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/ | grep 14. | xargs echo

      VERSIONS_TO_REMOVE_IN_16_0 = %w[14.0.0 14.0.1 14.0.2 14.0.3 14.0.4 14.0.5 14.0.6 14.1.0 14.1.1 14.1.2 14.1.3].freeze

/cc @matt_wilson