Group the CLI release workflow names
Rename the CLI release workflows to "CLI Release <channel>" so they sort together in the Actions list: Crates.io, GitHub, Homebrew, NPM, NuGet, PyPI, Scoop and winget. Workflows are dispatched by file name, so no trigger changes. The MCP Registry doc now uses the new NuGet name. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Seto Elkahfi committed
Oct 20, 2026 at 10:53 UTC
c3138dd33be5b59590616a5d9b9238f9c724eaca
9 files changed
+10
-10
.github/workflows/release-crate.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: Crates.io CLI Release
1
+name: CLI Release Crates.io
2
3
on:
4
push:
.github/workflows/release-github.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: GitHub CLI Release
1
+name: CLI Release GitHub
2
3
on:
4
workflow_dispatch:
.github/workflows/release-homebrew.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: Homebrew CLI Release
1
+name: CLI Release Homebrew
2
3
on:
4
workflow_dispatch:
.github/workflows/release-npm.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: NPM CLI Release
1
+name: CLI Release NPM
2
3
on:
4
workflow_dispatch:
.github/workflows/release-nuget.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: NuGet CLI Release
1
+name: CLI Release NuGet
2
3
on:
4
workflow_dispatch:
.github/workflows/release-pypi.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: PyPI CLI Release
1
+name: CLI Release PyPI
2
3
# Windows arm64 wheels are intentionally not built here. GitHub's hosted
4
# Windows runners provide x64 Python, and maturin refuses to build an arm64
.github/workflows/release-scoop.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: Scoop Release
1
+name: CLI Release Scoop
2
3
# Dispatched by release-github.yml once the release and its checksums exist.
4
on:
.github/workflows/release-winget.yml
+1
-1
@@ -1,4 +1,4 @@
1
-name: winget Release
1
+name: CLI Release winget
2
3
# Dispatched by release-github.yml once the release and its checksums exist.
4
#
docs/mcp-registry.md
+2
-2
@@ -73,8 +73,8 @@ per package — and both are updated by `make patch | minor | major` along with
73
the rest of the release metadata (`scripts/sync-release-version.mjs`).
74
75
Publishing is chained off the release: pushing a `v*` tag runs the crates.io
76
-workflow, which fans out to the distribution workflows, and **NuGet CLI
77
-Release** triggers **MCP Registry Release** once its publish job succeeds. It
76
+workflow, which fans out to the distribution workflows, and **CLI Release NuGet**
77
+triggers **MCP Registry Release** once its publish job succeeds. It
78
hangs off NuGet rather than the fan-out because the listing needs both npm and
79
NuGet live at that version, and NuGet is the slower of the two.
80