fix: satisfy npm trusted publishing requirements

Run the release workflow on a supported Node.js version and align package repository metadata with npm's GitHub trusted publishing checks. Update the release guide to document the exact repository URL and runtime expectations needed for CI publishes.

Author: shantur

.github/workflows/release.yml

@@ -20,12 +20,12 @@ jobs:
 
     steps:
       - name: Check out repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
 
       - name: Set up Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
-          node-version: 20
+          node-version: 24
           cache: npm
           registry-url: https://registry.npmjs.org
 

docs/setup/RELEASING.md

@@ -29,6 +29,7 @@ Critical npm-side details:
 - Workflow filename: `release.yml`
 - If you use an optional environment in npm's Trusted Publisher settings, it must exactly match the GitHub Actions environment name used by the workflow.
 - `package.json` must include a `repository.url` that exactly matches `https://github.com/NeuralNomadsAI/NomadWorks`.
+- GitHub Actions must run on a supported Node.js version for npm Trusted Publishing. This workflow uses Node.js `24`.
 
 No `NPM_TOKEN` repository secret is required once Trusted Publishing is configured correctly.
 

package.json

@@ -3,7 +3,7 @@
   "version": "0.1.0",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/NeuralNomadsAI/NomadWorks.git"
+    "url": "https://github.com/NeuralNomadsAI/NomadWorks"
   },
   "type": "module",
   "main": "dist/index.js",