Release Container Scanning v6
Proposal
Similar to Release Gemnasium v4 (#408528 - closed), we need to release a new version of container-scanning to coincide with the new major release 16.0
of GitLab
Implementation Plan
Steps to Release Container Scanning v6.
-
Create v6.x
branch frommaster
-
Implement Remove deprecated Container Scanning variables ... (#371840 - closed) with a target of v6.x
-
Create v5.x
branch frommaster
and make it protected -
Release 6.0.0
tag to publishregistry.gitlab.com/security-products/container-scanning:6
-
Verified that a CS scan with container-scanning:6
,container-scanning/trivy:6
,container-scanning/grpe:6
works -
Update gitlab monolith -
Update CS_ANALYZER_IMAGE
to"$CI_TEMPLATE_REGISTRY_HOST/security-products/container-scanning:6"
in CI template. -
Update user documentation -
Update references to Docker images. -
Monitor that Upgrade Container Scanning analyzer to version 6 (!118947 - merged) is merged
-
-
Merge v6.x
intomaster
. -
Update trigger-db-update
scheduled pipelineTRIGGER_DB_UPDATE_FOR_MAJOR_VERSIONS
variable to either4,5,6
or5,6
. Depends on this thread
Verification steps
On GitLab 16.x, run a new pipeline in a project where the Container Scanning CI template is included.
- ensure the container scanning job successfully runs the
container-scanning:6
image.
Edited by Shao Ming Tan