[llvm] [llvm][release] Describe types of release package on the release page (PR #138144)

[via llvm-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {darker}-->


:warning: Python code formatter, darker found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
darker --check --diff -r HEAD~1...HEAD llvm/utils/release/github-upload-release.py
``````````

</details>

<details>
<summary>
View the diff from darker here.
</summary>

``````````diff
--- github-upload-release.py	2025-05-01 15:04:25.000000 +0000
+++ github-upload-release.py	2025-05-01 15:07:42.391206 +0000
@@ -43,11 +43,12 @@
 
     if not message:
         # Note that these lines are not length limited because if we do so, GitHub
         # assumes that should be how it is laid out on the page. We want GitHub to
         # do the reflowing for us instead.
-        message = dedent("""\
+        message = dedent(
+            """\
 LLVM {} Release
 
 # Package Types
 
 * If the file name starts with `LLVM-` then it is a binary release of all of LLVM for the platform at the end of the file name. For example, `LLVM-20.1.1-Linux-ARM64.tar.xz` contains LLVM binaries for Arm64 Linux.

``````````

</details>


https://github.com/llvm/llvm-project/pull/138144