chore: bump version 1.4.1 -> 1.5.0 (publish the management-mode split) #54
Reference in New Issue
Block a user
Delete Branch "chore/bump-1.5.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
MOLECULE_MCP_MODE=managementregistry split (#50, merged 06-07) never got a version bump, so the published npm 1.4.1 tarball predates it — it serves only the 21 workspace a2a tools (grep isManagementMode dist/index.json the registry tarball = 0 hits).Consequence (found in the agents-team platform-agent pilot today): the
molecule-platform-agentimage bakes@molecule-ai/mcp-server@1.4.1, so the org concierge has no org-admin tools even with the mode env set —TOOLS-FAIL: mcp__platform__list_workspaces not found, verified over direct stdio in the live container.This PR only bumps
package.json/lock to 1.5.0. After merge, taggingv1.5.0triggers publish.yml; the template repo then bumpsMCP_VERSION=1.5.0inDockerfile.platform-agent(separate PR).🤖 Generated with Claude Code
Security 5-axis — APPROVE. chore: bump @molecule-ai/mcp-server 1.4.1→1.5.0 (package.json + package-lock.json only, +3/-3). Pure version pin — publishes the 1.5.0 line that carries the #53 create_issue tool. Zero code/logic surface, no dependency changes (deps block unchanged), no secrets. Gate GREEN (CI/test ✓). Author core-devops ≠ me. Trivial + safe → APPROVE; 2nd genuine lane → merge.
qa APPROVE (5-axis). Correctness: package.json + package-lock.json both move 1.4.1→1.5.0 consistently (lockfile root + package entry); no code delta. Robustness: publish-version bump — the npm release for #53's create_issue tool; nothing to test beyond CI-green. Security: no secrets/attack-surface; metadata only. Performance: n/a. Readability: trivial. CI/test green, mergeable. Pairs with tmpl-claude-code#107 (the bake consumes this publish → merge #54 first). Approving.