Skip to content

v0.3.1

Choose a tag to compare

View all tags
@galatanovidiu galatanovidiu released this 06 May 08:21
· 16 commits to trunk since this release
v0.3.1
80c68a2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What

Patch release. Roll-forward of v0.3.0, which never landed on npm.

Changes since 0.3.0

  • Fix package.json repository.url to point to github.com (was github.a8c.com, the internal mirror) so npm provenance verification matches the OIDC issuer.

Carries forward from v0.3.0 (never published)

Update @automattic/mcp-wordpress-remote from ^0.2.21 → ^0.3.1. Highlights:

  • WPCOM session refresh fix — broaden expired-session detection to match WPCOM error code -32005, the message Session not found, and JSON-RPC errors nested under error. Previously these surfaced as hard auth failures instead of triggering an automatic re-auth. (upstream #60)
  • SSE response support — handle text/event-stream from the WordPress MCP endpoint in addition to application/json. (upstream #51)
  • OAuth token directory fix — tokens now land in the correctly versioned ~/.mcp-auth/wordpress-remote-<version>/ subdirectory instead of wordpress-remote-undefined/. (upstream #52)
  • Recover from expired session errors — single in-flight refresh instead of failing the request. (upstream #53)
  • Don’t block MCP initialization on OAuth callback server shutdown — first-run OAuth no longer times out at 30s after the browser flow completes.

CI

.github/workflows/release.yml publishes to npm automatically on GitHub Release publish, via npm Trusted Publishing (OIDC). This is the first release using that flow.

PRs in this release

  • #3 chore: bump to 0.3.0 and update mcp-wordpress-remote to ^0.3.1
  • #4 ci: publish to npm on GitHub release
  • #5 fix: point repository.url to github.com and bump to 0.3.1
Assets 2
Loading