Codeman maintainer f66a9a574d ci: publish each release to the MCP registry ...

The registry does not follow npm, so every release waited on a by-hand
mcp-publisher publish, behind a browser login that expires between
releases.

Release now calls publish-mcp.yml once npm took a release. It signs in
with the workflow's OIDC token, which the registry accepts for the
io.github.Ark0N/ namespace, so it needs no secret and no browser. It skips
a version the registry already has, waits until npm serves a new one, and
can be run by hand with gh workflow run publish-mcp.yml.

The id-token right sits on its own job, which runs nothing from the
repository: it reads server.json and runs one pinned, checksummed binary.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-06 12:43:32 +01:00

..

browser-suite.yml

chore: bump Playwright to 1.64.1 and unpin the browser suite

2026-11-05 14:22:41 +01:00

ci.yml

feat(install): install without administrator rights (--no-admin)

2026-11-05 18:50:58 +01:00

publish-mcp.yml

ci: publish each release to the MCP registry

2026-11-06 12:43:32 +01:00

release.yml

ci: publish each release to the MCP registry

2026-11-06 12:43:32 +01:00

wiki-sync.yml

docs: publish docs/wiki as the user manual, with a sync workflow

2026-08-18 16:20:43 +02:00