remove semantic-release job

Author: domantas-jurkus-dcd

.agents/AGENTS.md

@@ -28,6 +28,11 @@ server.
 - After generating the tool, call the tool to actually test it.
 - When testing by calling the tool, prefer to not set the `jsRender` parameter.
 
+# Releasing
+
+- When bumping server versions, make sure all instances of the old server version are updated. These
+  are in `package.json`, `server.json` and possibly in other files.
+
 # Documentation
 
 - Update readme with new tool, toolset and parameter information.

.github/workflows/release.yml

@@ -11,56 +11,7 @@ concurrency:
   cancel-in-progress: false
 
 jobs:
-  semantic-release:
-    runs-on: ubuntu-latest
-    outputs:
-      released: ${{ steps.release.outputs.released }}
-      tag: ${{ steps.release.outputs.tag }}
-    permissions:
-      contents: write
-      issues: write
-      pull-requests: write
-      id-token: write
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 0
-          persist-credentials: true
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v5
-        with:
-          node-version: 'lts/*'
-          registry-url: 'https://registry.npmjs.org'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Build
-        run: npm run build --if-present
-
-      - name: Semantic release
-        id: release
-        env:
-          GH_TOKEN: ${{ secrets.GH_TOKEN }}
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: |
-          set -e
-          BEFORE=$(git describe --tags --abbrev=0 2>/dev/null || true)
-          npx semantic-release
-          AFTER=$(git describe --tags --abbrev=0 2>/dev/null || true)
-          if [ -n "$AFTER" ] && [ "$BEFORE" != "$AFTER" ]; then
-            echo "released=true" >> "$GITHUB_OUTPUT"
-            echo "tag=$AFTER" >> "$GITHUB_OUTPUT"
-          else
-            echo "released=false" >> "$GITHUB_OUTPUT"
-          fi
-
   mcp-publish:
-    needs: semantic-release
-    if: needs.semantic-release.outputs.released == 'true'
     runs-on: ubuntu-latest
     permissions:
       id-token: write
@@ -70,7 +21,7 @@ jobs:
       - name: Checkout tag
         uses: actions/checkout@v5
         with:
-          ref: ${{ needs.semantic-release.outputs.tag }}
+          ref: main
 
       - name: Setup Node.js
         uses: actions/setup-node@v5

CONTRIBUTING.md

@@ -1 +1,28 @@
-# Contributing
+# Publishing
+
+When After merging changes to the server, the following steps need to be done:
+
+1. Server version bump (major/minor/patch)
+
+2. Publish to MCP registry.
+
+## Server version bump
+
+Publishing is done manually through a developer machine. This enabled bundling multiple
+features/fixes under one release.
+
+When you want to publish a new version:
+
+- Pull `main` locally.
+
+- Bump the server version numbers in the following files: `package.json`, `server.json`. Note that
+  there may be more files where the version number
+
+- Choose between major, minor or patch bump accordingly.
+
+- Run `npm publish`. This command should instruct you how to authenticate with NPM. The full command
+  should look like this:
+
+```
+NPM_CONFIG__AUTHTOKEN=<one_time_token>npm publish --access public
+```