Update CI/CD documentation and workflows for multi-OS executable publishing

Author: sylvain-guillet

.github/workflows/release.yml

@@ -2,18 +2,17 @@ name: Release single-file (server.Stdio)
 
 on:
   workflow_dispatch:
-    inputs:
-      rid:
-        description: ".NET Runtime Identifier (e.g., linux-x64, win-x64, osx-arm64)"
-        required: true
-        default: "linux-x64"
   push:
     tags:
       - "v*"
 
 jobs:
   publish:
     runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        rid: [ linux-x64, win-x64, osx-arm64 ]
     steps:
       - name: Checkout
         uses: actions/checkout@v4
@@ -30,7 +29,7 @@ jobs:
         id: publish
         shell: bash
         env:
-          RID: ${{ github.event.inputs.rid || 'linux-x64' }}
+          RID: ${{ matrix.rid }}
         run: |
           set -euo pipefail
           PROJ="Server.Stdio/Server.Stdio.csproj"
@@ -63,6 +62,6 @@ jobs:
       - name: Upload executable artifact
         uses: actions/upload-artifact@v4
         with:
-          name: io-aerosapce-mcp-${{ github.ref_name }}-${{ github.event.inputs.rid || 'linux-x64' }}
+          name: io-aerosapce-mcp-${{ github.ref_name }}-${{ matrix.rid }}
           path: ${{ steps.publish.outputs.exe }}
           if-no-files-found: error

docs/CI-CD.md

@@ -1,21 +1,27 @@
 # CI/CD
 
 - CI: Builds the repository on every push and PR (.github/workflows/ci.yml).
-- CD: Publishes a single-file executable for `server.Stdio` and uploads only that file as an artifact (.github/workflows/release.yml).
+- CD: Publishes single-file executables for `server.Stdio` for three OS targets in one run (.github/workflows/release.yml).
 
 How to trigger deployment:
 - Tag-based: push a tag like `v1.0.0`.
-- Manual: Actions → "Release single-file (server.Stdio)" → Run workflow and choose a RID (default `linux-x64`).
+- Manual: Actions → "Release single-file (server.Stdio)" → Run workflow (no inputs).
 
-Change target runtime:
-- Provide a different RID when running the workflow (examples: `linux-x64`, `win-x64`, `osx-arm64`).
+Targets built (one shot):
+- linux-x64, win-x64, osx-arm64
+
+Change targets:
+- Edit the matrix in `.github/workflows/release.yml` (key `matrix.rid`) to add/remove RIDs.
 
 Result:
-- Artifact name: `io-aerosapce-mcp-<tag or branch>-<RID>`
-- Contains only the produced executable.
+- Three artifacts:
+  - `io-aerosapce-mcp-<tag or branch>-linux-x64`
+  - `io-aerosapce-mcp-<tag or branch>-win-x64`
+  - `io-aerosapce-mcp-<tag or branch>-osx-arm64`
+- Each contains only the produced executable.
 
 Note on cross-publishing (ubuntu-latest):
-- Yes, you can generate Windows (.exe) or macOS binaries from Ubuntu by setting RID to `win-x64` or `osx-arm64`.
+- Yes, Windows and macOS binaries are generated on Ubuntu by setting the RID.
 - macOS outputs will be unsigned; signing/notarization must happen on macOS if required.
 
 Local single-file publish examples: