Label security release blog post as critical when applicable
Overview
When a security/patch release contains any critical changes (severity1), the generated blog post should be labeled as "Critical". The title should be updated to: GitLab Critical Security Release
.
These three places should be updated:
title: "GitLab Critical Security Release: 16.0.1"
description: "Learn more about GitLab Critical Security Release: 16.0.1 for GitLab Community Edition (CE) and Enterprise Edition (EE)."
canonical_path: "/releases/2023/05/23/critical-security-release-gitlab-16-0-1-released/"
This issue is a followup to https://gitlab.com/gitlab-com/gl-security/appsec/tooling/security-release-tools/-/merge_requests/76#note_1625873407.
Edited by Steve Abrams