From 3876449d5f8f51187c02281626759a4a15c0609c Mon Sep 17 00:00:00 2001 From: Daniel Engbert Date: Tue, 7 Apr 2026 23:02:03 +0200 Subject: [PATCH] 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 4474d35c7fbb..94f46ea9d80a 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