Clarify purpose of dependency list report
What does this MR do?
This is the first MR to address issues brought up by a customer in this ticket: https://gitlab.zendesk.com/agent/tickets/151538 (internal link)
There was some confusion (both on the part of the customer and the support team) about the reports from the dependency list and the dependency scanning job. I think that making this distinction on the dependency list doc, which is the only place to directly download a report involving dependencies, is a good start.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team