jpandClaude Opus 4.7
713a5c79bf
Two fixes from Copilot's 2026-04-23 inline review: 1. Drop `-n` from the grep command. Hard-coded line numbers in the "Expected" block would drift as files evolve, making the checklist misleading. The check is about presence, not location — line numbers add noise without helping pass/fail. 2. Reword "`console_script` entry point declared in pyproject.toml" → "console script declared under `[project.scripts]` in pyproject.toml". PEP 621's `[project.scripts]` is the canonical name for this repo's config form; the old wording conflated it with setuptools' `console_scripts` entry-point group name. Expected output block updated to match new grep (no colons before line numbers). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Releasing MemPalace
Pre-release checklist
Run from the repo root before cutting a release tag.
Verify mempalace-mcp entry point alignment
The plugin configs reference mempalace-mcp as the MCP server command, which
resolves to a console script declared under [project.scripts] in
pyproject.toml. If these disagree, pip install mempalace ships a plugin
config pointing at a binary that was never installed — exactly what broke
v3.3.2 (#1093).
grep -r mempalace-mcp pyproject.toml .claude-plugin .codex-plugin
Expected on a healthy develop (post-#340) — one line per file:
pyproject.toml:mempalace-mcp = "mempalace.mcp_server:main"
.claude-plugin/plugin.json: "command": "mempalace-mcp"
.codex-plugin/plugin.json: "command": "mempalace-mcp"
.claude-plugin/.mcp.json: "command": "mempalace-mcp"
If pyproject.toml has no match, stop — the entry point is missing and
any fresh pip install will ship a broken plugin config. Investigate whether
the release branch was cut before
#340 landed on develop.