Secret-detection-0 appear in the list of Jobs even when secret detection templated is not added to pipeline

Since 12 Jul 2023, a new job has appeared as secret-detection-0 in the test stage.

This new job is enabled even if the secret detection template is not added to the pipeline.

After some testing, I discovered that if you enable any SAST, then this job appears and I cannot override it and because I use a default before_script, then the job fails and the pipeline finishes with a warning instead of success.

Looks like is related to this change. Run SAST and Dependency Scanning from enforced policies in same pipeline (3573e97e) · Commits · / GitLab · GitLab

Anyone from Gitlab can help here?