chore(mcp-server): bump 0.14.0 → 0.14.1 for first keigit publish
Pre-tag bump. publishConfig.registry already pinned to https://keigit.com/api/packages/keisei/npm/. KEIGIT_TOKEN secret configured on github KeiSei84/KeiSeiKit-1.0 repo. keigit org `keisei` (id=5) created and verified live. Verification: - `npm run build --workspace=@keisei/mcp-server` exits 0 [REAL: ran in this session] - dist/index.js produced (4125 bytes) - Token works: `GET /api/v1/user` with PAT → 200 - Registry empty: `GET /api/packages/keisei/npm/` → 404 (expected) After tag v0.14.1 pushes, the release workflow's npm-publish job runs `npm publish --access public` which routes via publishConfig to keigit. Expected: package lands at https://keigit.com/keisei/-/packages/npm/@keisei%2Fmcp-server Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
784dfbae6f
commit
da819a0d92
2 changed files with 2 additions and 2 deletions
2
_ts_packages/package-lock.json
generated
2
_ts_packages/package-lock.json
generated
|
|
@ -3707,7 +3707,7 @@
|
|||
},
|
||||
"packages/mcp-server": {
|
||||
"name": "@keisei/mcp-server",
|
||||
"version": "0.14.0",
|
||||
"version": "0.14.1",
|
||||
"license": "Apache-2.0",
|
||||
"dependencies": {
|
||||
"@modelcontextprotocol/sdk": "^1.0.0",
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@keisei/mcp-server",
|
||||
"version": "0.14.0",
|
||||
"version": "0.14.1",
|
||||
"description": "MCP server exposing KeiSeiKit Rust primitives as Model Context Protocol tools — published to keigit.com (Forgejo npm registry, public DNS)",
|
||||
"type": "module",
|
||||
"main": "./dist/index.js",
|
||||
|
|
|
|||
Loading…
Reference in a new issue