SASTBot: Monthly dependency updates for 17.2
requested to merge gitlab-org/security-products/analyzers/sast-bot/secrets-forked:sast-bot-243 into master
What does this MR do?
- Upgrade
Gitleaks
version [8.18.3
=>8.18.4
] (!313 (merged)) - Upgrade
gitlab.com/gitlab-org/security-products/analyzers/report/v5
version [v5.1.0
=>v5.2.1
] (!313 (merged)) - Upgrade
gitlab.com/gitlab-org/security-products/analyzers/ruleset/v3
version [v3.0.0
=>v3.1.0
] (!313 (merged)) - Upgrade
Security Report Schemas
to15.1.4
(!313 (merged))
CHANGELOG is generated by SASTBot.
Note: We updated security-report-schemas because it was updated in the report
module when it was bumped from v5.1.0
to v5.2.1
.
I have additionally ran analyzer-refresh-expected-json
to make sure any other json
used in tests is updated.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer
Edited by Ahmed Hemdan