pog-mcp 1.1.8 → 1.1.9

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog — pog-mcp
 
+## 1.1.9 — prepared, npm publication on security hold
+
+- Pin MCP SDK 1.32.0 to include the security fixes tracked in #1015. The
+  executable remains stdio-only; exported-server consumers adding HTTP must
+  separately configure input-element and request-body limits.
+- Update the test toolchain to the matched, patched Vitest 4.1.12 family.
+- Replace token-based GitHub publication with npm Trusted Publishing (OIDC),
+  using verified Node 24.22.1 / npm 11.19.1 and no credential fallback. Add the
+  repository metadata used to bind the package to its publishing workflow.
+- This version is prepared for review, **not yet published**. Under #778,
+  npm publication remains disabled until credential rotation, publish-history
+  verification and separate owner approval are complete. Merging this code
+  must not imply that existing npm users have received the update.
+
 ## 1.1.8 — 2026-10-14
 
 - Refresh bundled shared game rules and account ownership types for the common

package/README.md

@@ -61,21 +61,49 @@ claude mcp add proof-of-goal -- node /absolute/path/to/packages/mcp/dist/index.j
 
 ## Releasing
 
-Publishing is automated: merge to `main` with a new `version` in `package.json`
+Publishing is on a **security hold (#778)**. The release workflow requires the
+repository Actions variable `POG_NPM_PUBLISH_ENABLED` to equal `true`, as well
+as a non-PR run on `main`; an absent effective value or `false` skips the whole publish
+job before it can request an OIDC credential. Re-enable only after credential
+revocation/rotation, publication-history verification and separate owner
+approval following [the operator checklist](https://github.com/1XP-AI/solana-world-soccer-2026/blob/main/SECURITY-FOLLOWUPS.md#npm-778-npm-publication-security-hold-2026-10-22).
+Keep the repository variable explicitly `false` rather than deleting an
+override of a possible organization value. Do not use manual publication to
+bypass this hold.
+
+After that approval, merge to `main` with a new `version` in `package.json`
 and `.github/workflows/publish-mcp.yml` puts it on npm. A pull request that
 changes shipped files (`src/`, `skill/`, `README.md`, the manifest) while the
 version is already on npm fails the check — npm cannot overwrite a version, so
 without the bump the merge would publish nothing and `npx -y pog-mcp` would keep
 handing out the old server.
 
-Two things are set up once, by hand:
-
-- **The first publish.** A granular token can only be scoped to a package that
-  exists, so the order is: `npm publish --access public` from this directory,
-  then create the token. Nothing to decide first — the licence is in place.
-- **`NPM_TOKEN`.** A granular npm access token with read-and-write rights on
-  this package, stored as the repository secret `NPM_TOKEN`. Nothing in CI can
-  create it.
+The PR version check and secret-free publish rehearsal remain enabled during
+the hold. A passing check or a merge does not lift it. Release setup is
+owner-operated:
+
+- **The first publish (already completed for `pog-mcp`).** A granular token
+  scoped to a package requires that package to exist. This bootstrap is not a
+  recovery step and must not be repeated to bypass the security hold.
+- **Trusted Publishing (OIDC).** In npm's `pog-mcp` Settings, authorize GitHub
+  owner `1XP-AI`, repository `solana-world-soccer-2026`, workflow filename
+  `publish-mcp.yml`, with direct publishing enabled. The workflow uses a fresh
+  GitHub-hosted runner, verified Node 24.22.1 / npm 11.19.1 and a short-lived
+  OIDC exchange; no `NPM_TOKEN` secret or token renewal is needed. PR checks
+  never receive `id-token: write`. Newly configured trust must be used within
+  npm's activation window (currently two days).
+- After the first verified OIDC publication, revoke any temporary npm token
+  and remove the old `NPM_TOKEN` Actions secret. Trusted Publishing does not
+  revoke credentials by itself. Require 2FA and disallow bypass tokens in the
+  package settings; these settings do not disable Trusted Publishing.
+- This repository stays private, so the publish command explicitly disables
+  provenance (npm provenance requires a public source repository). OIDC
+  authentication still works. Never make the repository public to enable it.
+
+See [npm's Trusted Publishing documentation](https://docs.npmjs.com/trusted-publishers/)
+for the provider requirements. A successful dry-run verifies packaging, not the
+registry's OIDC authorization; verify the actual release run and registry
+version, `gitHead`, integrity and `latest` tag after publication.
 
 ## Licence
 

package/package.json

@@ -1,10 +1,15 @@
 {
   "name": "pog-mcp",
-  "version": "1.1.8",
+  "version": "1.1.9",
   "type": "module",
   "description": "MCP server that lets an AI agent play Proof of Goal — wallet, sign-in, squad building, and matches as typed tools.",
   "license": "MIT",
   "homepage": "https://pog.soccer/agents",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/1XP-AI/solana-world-soccer-2026.git",
+    "directory": "packages/mcp"
+  },
   "keywords": [
     "mcp",
     "model-context-protocol",
@@ -48,7 +53,7 @@
     "prepublishOnly": "pnpm build"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.13.0",
+    "@modelcontextprotocol/sdk": "1.32.0",
     "@noble/curves": "^1.8.2",
     "@noble/hashes": "^1.8.0",
     "@scure/bip39": "^1.6.0",
@@ -57,8 +62,8 @@
   },
   "devDependencies": {
     "@types/node": "^22.15.30",
-    "@vitest/coverage-v8": "^3.2.4",
+    "@vitest/coverage-v8": "4.1.12",
     "typescript": "*",
-    "vitest": "^3.2.4"
+    "vitest": "4.1.12"
   }
 }