Skip to content

Label blog post as critical when containing s1 issues

Steve Abrams requested to merge delivery19791-critical-label into master

🔎 What does this MR do and why?

When a patch release contains an S1, or critical, issue, the generated blog post is labeled as a "Critical release".

Related to gitlab-com/gl-infra/delivery#19791 (closed)

🛠 Testing

I generated two blog posts by running the release:patch_blog_post rake task with dry run enabled TEST=true.

First we see one without any S1 issues, so it is not a critical release (we just finished a security release, so there are not really any issues linked yet). I've left out the bulk of the blog content since it remains unchanged.

---
title: "GitLab Security Release: 16.5.2, 16.4.3, 16.3.7"
categories: releases
author: ADD_YOUR_FULL_NAME
author_gitlab: steveabrams
author_twitter: gitlab
description: "Learn more about GitLab Security Release: 16.5.2, 16.4.3, 16.3.7 for GitLab Community Edition (CE) and Enterprise Edition (EE)."
canonical_path: '/releases/2023/11/07/security-release-gitlab-16-5-2--16-4-3--16-3-7-released.html.md'
image_title: '/images/blogimages/security-cover-new.png'
tags: security
---

Next I modified the code to mark the release as critical if there are any S1 - S4 issues (so any issue). We see the updated header:

---
title: "GitLab Critical Security Release: 16.5.2, 16.4.3, 16.3.7"
categories: releases
author: ADD_YOUR_FULL_NAME
author_gitlab: steveabrams
author_twitter: gitlab
description: "Learn more about GitLab Critical Security Release: 16.5.2, 16.4.3, 16.3.7 for GitLab Community Edition (CE) and Enterprise Edition (EE)."
canonical_path: '/releases/2023/11/07/critical-security-release-gitlab-16-5-2--16-4-3--16-3-7-released.html.md'
image_title: '/images/blogimages/security-cover-new.png'
tags: security
---

✔ Author Check-list

  • [-] Has documentation been updated?

Merge request reports