From 68ebc987ee06b7affffc5789fa32974ab8bb461c Mon Sep 17 00:00:00 2001 From: Daniel Engbert Date: Tue, 7 Apr 2026 23:02:03 +0200 Subject: [PATCH 1/3] bold text in immutable-releases.md --- .../concepts/supply-chain-security/immutable-releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/concepts/supply-chain-security/immutable-releases.md b/content/code-security/concepts/supply-chain-security/immutable-releases.md index 12cbdaa97cab..3b3c12851c9f 100644 --- a/content/code-security/concepts/supply-chain-security/immutable-releases.md +++ b/content/code-security/concepts/supply-chain-security/immutable-releases.md @@ -26,7 +26,7 @@ Additionally, creating an immutable release automatically generates a **release > [!NOTE] > Immutable releases include protection against repository resurrection attacks. Even if you delete a repository and create a new one with the same name, you cannot reuse tags that were associated with immutable releases in the original repository. -If a release is immutable, you will see "{% octicon "lock" aria-hidden="true" %} Immutable" below the title on the release page. +**If a release is immutable, you will see "{% octicon "lock" aria-hidden="true" %} Immutable" below the title on the release page.** ## Best practices for publishing immutable releases From 729f8cf0f361f716b493f66996dba36436b0f6a6 Mon Sep 17 00:00:00 2001 From: Daniel Engbert Date: Sun, 17 May 2026 06:18:45 -0400 Subject: [PATCH 2/3] Update immutable-releases.md Address feedback --- .../concepts/supply-chain-security/immutable-releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/concepts/supply-chain-security/immutable-releases.md b/content/code-security/concepts/supply-chain-security/immutable-releases.md index 3b3c12851c9f..7e7115e78a64 100644 --- a/content/code-security/concepts/supply-chain-security/immutable-releases.md +++ b/content/code-security/concepts/supply-chain-security/immutable-releases.md @@ -26,7 +26,7 @@ Additionally, creating an immutable release automatically generates a **release > [!NOTE] > Immutable releases include protection against repository resurrection attacks. Even if you delete a repository and create a new one with the same name, you cannot reuse tags that were associated with immutable releases in the original repository. -**If a release is immutable, you will see "{% octicon "lock" aria-hidden="true" %} Immutable" below the title on the release page.** +If a release is immutable, you will see "{% octicon "lock" aria-hidden="true" %} **Immutable**" below the title on the release page. ## Best practices for publishing immutable releases From f2c5539329f5df52fb47fe55453e64cbc6f66a6c Mon Sep 17 00:00:00 2001 From: Sharra-writes Date: Mon, 18 May 2026 21:17:25 -0700 Subject: [PATCH 3/3] Apply suggestion from @Sharra-writes --- .../concepts/supply-chain-security/immutable-releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/concepts/supply-chain-security/immutable-releases.md b/content/code-security/concepts/supply-chain-security/immutable-releases.md index 7e7115e78a64..08757f152b7f 100644 --- a/content/code-security/concepts/supply-chain-security/immutable-releases.md +++ b/content/code-security/concepts/supply-chain-security/immutable-releases.md @@ -26,7 +26,7 @@ Additionally, creating an immutable release automatically generates a **release > [!NOTE] > Immutable releases include protection against repository resurrection attacks. Even if you delete a repository and create a new one with the same name, you cannot reuse tags that were associated with immutable releases in the original repository. -If a release is immutable, you will see "{% octicon "lock" aria-hidden="true" %} **Immutable**" below the title on the release page. +If a release is immutable, you will see {% octicon "lock" aria-hidden="true" %} **Immutable**" below the title on the release page. ## Best practices for publishing immutable releases