Release 0.1.27

[elemdos]

Release 0.1.27

Bumps primo-cli to 0.1.27. Everything since the published 0.1.25 (0.1.26 was bumped but never published).

New — agent setup and preview

• primo mcp install / mcp list / mcp print — wire the official primo-mcp server into the clients on your machine (Claude Code, Claude Desktop, Cursor, VS Code / Copilot, Codex, OpenCode, Gemini CLI, Cline, Windsurf, Continue, Zed). Merges only the primo entry, preserves everything else, backs up, idempotent. (Add primo mcp install for multi-client MCP setup #27)
• primo init wires MCP clients — detects them and offers to connect, so a fresh workspace has Primo tools before the first agent session. --yes / --no-mcp; primo-mcp is now a dependency. (Wire Primo MCP during primo init #28)
• primo status — workspace, server, sites, groups, and last-import state, with --json; reads live CMS state via the local dev token when the server is up. (Add primo status — workspace, server, sites, and sync state #34)
• primo preview — regenerate a site's published preview from the CLI (no MCP client needed); primo new generates it so the URL it prints actually works. (Add primo preview — rebuild a site's published preview from the CLI #35)

Fixed — correctness and build signals

• primo validate rejects YAML primo build can't parse — pages, block content.yaml, page-type layout.yaml, site/content.yaml. (Reject page and content YAML the build cannot parse #29)
• primo build — page sections fall back to block defaults; a comment-only layout.yaml (what primo new scaffolds) no longer crashes the build; generated head bindings stop flooding Svelte's state_referenced_locally warning; and a page that renders the fallback error page now fails the build (non-zero) instead of exiting 0. (Fix page-section defaults, comment-only layouts, head warnings, and silent failures in primo build #33)
• Group ids — primo dev / primo add explain that the server assigns group ids on import and matches by name; the CLI writes the server-assigned id back to server.yaml / site.yaml. (Explain that Primo assigns site-group ids on import #32)
• primo add — reports "already registered — re-imported" on a re-run, and site_exists authenticates so existing sites take the additive import path rather than bootstrap. (Authenticate site_exists; make primo add re-runs legible #37)
• primo new — no longer hand-authors _ids (the server mints them) and now emits page-types/default/head.svelte + the seo_* fields. (Drop hand-authored _ids from the primo new scaffold; add page-type head #36)
• Display name — primo new harrow-stone now yields Harrow Stone. (Title-case the display name derived from a site's folder #31)
• Site-registration messaging clarified for primo add / primo new. (Clarify site-registration messaging in primo add and primo new #30)

Sequencing

• Publish primo-mcp 0.1.8 first — primo preview's happy path needs its primo-mcp/compiler subpath (mcp Fix dev watcher silently dropping re-created files #18). The command degrades with a clear message on older primo-mcp.
• The group-id writeback and nested-index _id fix depend on a server (binary) release containing primocms/primo #1243 / #1244.
• Docs (docs Accept body sections in layout.yaml #2 / Refresh stale server binary instead of reusing it forever #3, already merged) only match npm once this publishes.

Summary by CodeRabbit

• Chores
  • Updated the primo-cli package version to 0.1.27.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 6374258b-89fe-4992-8597-960dc5418371

📥 Commits

Reviewing files that changed from the base of the PR and between 7f601a7 and fdc1dfd.

📒 Files selected for processing (1)

• package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The primo-cli package version changes from 0.1.26 to 0.1.27 in package.json.

Changes

Package version update

Layer / File(s)	Summary
Update package version package.json	The package version changes from 0.1.26 to 0.1.27.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to fdc1d

The version metadata mismatch is optional synchronization and does not block release workflows.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the release version, which matches the package version change from 0.1.26 to 0.1.27 and the stated release objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}