Skip to content

Add upstream scanner update process to CA handbook

Olivier Gonzalez requested to merge CA_add_upstream_scanner_update_process into master

Why is this change being made?

Follow up from the !80525 (merged), this MR adds details on steps to follow when updating an upstream scanner. We want to make sure we scan for possible new vulnerabilities on the newer version before using it.

This is based on this OKR: #10444 (closed)

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)
Edited by Olivier Gonzalez

Merge request reports