Remove 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 announced in #366477 (closed), all security report schemas that match 14.*.*
were deprecated in GitLab %15.8.
This issue is for the removal of said schemas in GitLab %16.0.
Breaking Change
Any security scanner integrations that use a deprecated schema version cause a warning to display on the pipeline security tab.
In GitLab %16.0, these warnings become errors, and the security report will not be ingested by GitLab.
Vendors must update their reports to utilize a supported schema. As of GitLab %15.4, schema versions 15-x-x
are the latest versions supported.
Affected Topology
Affected Tier
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
- If there is no stable counterpart listed for Sales/CS please mention
- To see who the stable counterparts are for a product team visit product categories
-
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
Deprecated in 15.8
Planned Removal Milestone
Links
/cc @matt_wilson
Implementation plan
-
Remove all 14.X.X schemas from ee/lib/ee/gitlab/ci/parsers/security/validators/schemas
-
Remove all references to removed schemas from lib/gitlab/ci/parsers/security/validators/schema_validator.rb
-
Fix broken specs including E2E specs which ingest 14.X.X security schema reports