Skip to content

Editorial Publisher for ChatGPT 1.0.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Jul 06:34
· 102 commits to main since this release
v1.0.1
478c3ec

Editorial Publisher for ChatGPT 1.0.1

Editorial Publisher for ChatGPT connects a self-hosted WordPress site to ChatGPT through an open-source OAuth 2.1 MCP service. It supports compact content discovery, selected retrieval, draft creation and revision, media, taxonomy, normalized SEO metadata, preview, scheduling, and publishing without an OpenAI API key or built-in LLM call.

Consequential actions are deliberately gated: editorial connections cannot publish, and publisher actions require a fresh single-use confirmation bound to the connection, content version, and intended action. WordPress independently rechecks the connection scope and the approving user's current native capability.

The release includes:

  • editorial-publisher-for-chatgpt-1.0.1.zip for WordPress upload
  • source archive and SHA-256 checksums
  • CycloneDX production SBOM
  • Docker/Compose, standard Node 24, and Vercel Function deployment templates
  • signed public AMD64/ARM64 image at ghcr.io/asimons81/wp-chatgpt-publisher:1.0.1
  • architecture, threat model, privacy/terms templates, self-hosting, reviewer workflow, and submission materials
  • automated unit, PHP, integration, E2E, security, lifecycle, compatibility, and packaging gates

This patch adds the promised opt-in, low-cardinality /metrics endpoint and completes structured tool-operation logging. Connection identifiers are hashed, content and credentials remain excluded, and metrics are disabled by default.

The container image is publicly pullable at digest sha256:4c44873b2e5abb050fdfde0763fd1bf15ce12cc4da34a02d16c033afec1417d5. Its GitHub Actions SLSA provenance is embedded in GHCR and verifies against .github/workflows/container.yml.

Known v1 exclusions include Multisite, WordPress.com hosted plans, headless sites, disabled REST API environments, AIOSEO writes, permanent deletion, broad site administration, code/filesystem/database execution, autonomous generation/publishing, and built-in OpenAI API calls.

The production MCP endpoint is deployed with durable PostgreSQL and passes public readiness, OAuth, persistence, UI-asset, and authentication-challenge checks. ChatGPT desktop developer-mode OAuth, read, draft, and non-executing publish-review acceptance passes. Current OpenAI guidance says MCP apps are web-only, so mobile-client acceptance is not applicable. Recreating the developer app for the expanded desktop matrix and completing the WordPress.org/OpenAI submissions require the owner's OpenAI developer identity verification plus final privacy, terms, support, reviewer-account, and portal confirmations.

Assets 6
Loading