You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5803eed
Browse filesBrowse the repository at this point in the historyBrowse files
The v1.3.1 publish failed with a 403: "Two-factor authentication is
required to publish this package but an automation token was specified".
The token that published v1.3.0 is no longer accepted, as the npm
restriction on 2FA-bypass tokens anticipated.
Switch the npm step to trusted publishing (OIDC). Drop `registry-url:` on
setup-node, the NPM_TOKEN credential check, and the NODE_AUTH_TOKEN env:
with no token, the auth line setup-node writes into .npmrc would block
the OIDC exchange (actions/setup-node#1551).
Requires the trusted publisher registered on npmjs.com for
akutishevsky/monobank-mcp-server, workflow publish.yml.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
# The version lives in five places (package.json, package-lock.json,
44
39
# manifest.json, both fields in server.json, and the McpServer
@@ -67,20 +62,6 @@ jobs:
67
62
check "src/index.ts" "$(grep -oE 'version: "[^"]+"' src/index.ts | head -1 | sed -E 's/.*"(.*)"/\1/')"
68
63
exit $fail
69
64
70
-
# An absent secret expands to an empty string rather than failing, and
71
-
# npm then reports it ten steps later as a bare "ENEEDAUTH ... you need
72
-
# to authorize this machine", which says nothing about the real cause.
73
-
# Fail here instead, with the fix in the message.
74
-
- name: Verify npm credentials are present
75
-
env:
76
-
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
77
-
run: |
78
-
if [ -z "${NODE_AUTH_TOKEN}" ]; then
79
-
echo "::error::The NPM_TOKEN secret is unset or empty. Create an npm Automation token (npmjs.com -> Access Tokens -> Generate New Token -> Automation) and add it under Settings -> Secrets and variables -> Actions as NPM_TOKEN."
80
-
exit 1
81
-
fi
82
-
echo "NPM_TOKEN is present"
83
-
84
65
- name: Install mcp-publisher
85
66
run: |
86
67
curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
@@ -115,23 +96,18 @@ jobs:
115
96
echo "exists=false" >> "$GITHUB_OUTPUT"
116
97
fi
117
98
118
-
# Authenticated with an npm Automation token. This is a stopgap: per
119
-
# the 2026-07-08 npm changelog, tokens that bypass 2FA lose the
120
-
# ability to publish directly in January 2027.
121
-
#
122
-
# To migrate to trusted publishing before then, register the publisher
123
-
# at https://www.npmjs.com/package/monobank-mcp-server/access
99
+
# Trusted publishing: npm exchanges the workflow's OIDC token for a
100
+
# short-lived publish credential, so there is no secret to store or
101
+
# rotate. Requires the trusted publisher registered at
0 commit comments