Changelog

What changed in each release of PromptWire.

1.5.0 (8 April 2026)

  • Changed: Module renamed from PW-MCP to PromptWire. Class names, file names, CLI scripts, API endpoints, and environment variables have all been updated.
  • Changed: Install directory is now site/modules/PromptWire/ (was PwMcp/).
  • Changed: On install or upgrade, the module automatically detects and removes old PwMcp/ and PwMcpAdmin/ directories.
  • Changed: Remote API file renamed to promptwire-api.php; config file to config-promptwire.php.
  • Changed: Environment variable PW_MCP_CLI_PATH renamed to PROMPTWIRE_CLI_PATH.
  • Changed: API key constant renamed from PW_MCP_API_KEY to PROMPTWIRE_API_KEY.
  • Kept: Data directories unchanged: .pw-sync/ for schema and site/assets/pw-mcp/ for content sync. No migration needed for existing data.
  • Fixed: Admin dashboard "Wire to File" exported pages to site/assets/promptwire/ instead of site/assets/pw-mcp/. One line in SyncManager.php was missed during the rename. Pull the latest from main for the fix. If any exports were created before updating, move them from site/assets/promptwire/ into site/assets/pw-mcp/ and delete the empty directory.

1.4.0 (8 April 2026)

  • Changed: Module restructured so the repo root is the module directory. Clone or download directly into site/modules/PwMcp/.
  • Changed: On install or upgrade, the module automatically detects and removes the old site/modules/PwMcpAdmin/ directory from pre-1.4.0 installs.
  • Fixed: schemaPush() routed to the remote API when both PW_PATH and PW_REMOTE_URL were set, so schema pushes silently went to production while reads used the local site. Now applies the same PW_PATH-first guard used elsewhere.
  • Fixed: validateRefs() defaulted to validating against the remote site when both env vars were set, inconsistent with the "local wins" rule. Now defaults to local when PW_PATH is present.
  • Fixed: pushPage() and publishPage() always returned success: true even when local or remote sub-operations failed. Failures were only visible in nested results. Top-level success now reflects actual outcome.
  • Fixed: publishPage() silently swallowed YAML parse errors and created remote pages with empty fields. Now reports the parse failure instead.
  • Improved: schemaPull() backs up existing fields.json and templates.json as .bak files before overwriting, so a mistaken pull is recoverable.
  • Improved: Remote API endpoint now sends X-Robots-Tag: noindex, nofollow header.

1.3.1 (27 March 2026)

  • Fixed: When both PW_PATH and PW_REMOTE_URL are set (hybrid config), runPwCommand now prefers the local PHP CLI. Previously PW_REMOTE_URL silently hijacked all commands, causing page queries to return stale remote data instead of live local data.
  • Fixed: Remote API endpoint now sends Cache-Control: no-store and Pragma: no-cache headers to prevent proxy or browser caching of API responses.

1.3.0 (27 March 2026)

  • New: pw_page_init tool for initialising or repairing page.meta.json for sync directories where content files were created manually.
  • Improved: pw_page_new is now idempotent. If the directory exists but page.meta.json is missing, it creates only the scaffold files without overwriting existing page.yaml or field files.
  • Improved: pw_page_publish auto-generates page.meta.json from page.yaml and directory structure when the meta file is missing.
  • Improved: Error messages in pw_page_push and pw_page_publish now show relative paths instead of absolute server paths, and include actionable hints.

1.2.0 (8 March 2026)

  • File sync, schema sync, cross-environment page ID resolution, remote API.

1.1.0 (5 February 2026)

  • Content sync (pull/push), page creation and publishing.

1.0.0 (29 January 2026)

  • Initial release. Site inspection, page queries, template/field introspection.