Add details about project & branches to security issues

Created on 28 March 2025, 28 days ago

To assist in triaging security issues, it is helpful to know what is supported for the project. The initial automated comment in GitLab should contain:

  • Does the project have security advisory coverage? If not, add a note that maintainers can use the issue to coordinate in private, but no advisory will be published. If covered, make sure the notes added are sufficient.
  • List what branches are currently supported. Create a branch in the private fork for each to draft any fixes.

Remaining tasks

With ๐Ÿ“Œ Remove โ€œrecommendedโ€ status for releases? Active done, we can migrate the project_release_supported_versions table to modern Drupal and will have the supported branch data to for this.

โœจ Feature request
Status

Active

Version

1.0

Component

Security advisories

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States drumm NY, US

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024