Files
codebase-memory-mcp/.github
Martin Vogel 4488959135 ci(release): correct channel semantics for semver prereleases
A version containing a prerelease suffix (v0.9.1-rc.1) now publishes as an
RC on every channel instead of masquerading as stable:

- GitHub release is created with prerelease: true (never marked Latest)
- npm publishes under the `next` dist-tag, so plain `npm install` keeps
  serving the last stable; testers opt in with codebase-memory-mcp@next
- the MCP Registry sync is skipped (the registry has no channel concept)
- PyPI needs no change: PEP 440 already treats rc versions as pre-releases
  that pip only installs with --pre

Stable releases (no dash) are byte-identical in behavior.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
2026-07-27 21:51:45 +02:00
..