v0.10.0 — Title format setting + version picker

New features

Configurable post title format

A new Post Titles setting under Settings → Post Creation lets you choose the shape of generated post titles:

• Plugin name and version (default, current behavior) — My Plugin v1.2 — New dashboard widget. Recommended for sites covering multiple projects.
• Version number only — Version 1.2 — New dashboard widget. Drops the project name from the prefix.
• No prefix — the AI writes the full title with no automatic prefix. Recommended for sites focused on a single project, where leading every title with the project name and version reads as repetitive across the archive.

In No prefix mode, the AI prompt is also tuned to vary title openings — encouraging shapes like "Faster transcripts and security fixes arrive in Project v1.2" or "v1.2 update adds Stable Diffusion image generation" instead of always opening with the project name.

Version picker for "Generate post"

When a repository has multiple GitHub releases, clicking Generate post now opens a picker so you can choose any historical release — useful for backfilling an archive of past releases, not just the latest one.

• Selected version with an existing post → an inline warning appears in the picker; generating creates a new revision and preserves the existing post date and slug.
• Older releases are automatically backdated to one hour after the GitHub publication time, so the archive stays in chronological order. You can adjust the date in the editor before publishing.
• After generation, a green checkmark appears next to the Generate post button — click it to jump straight to the new post in the editor.
• The "Last Post" column flash on the Repositories tab is suppressed when generating for a non-latest release (since the new post would not actually be the most recent).

For developers

• New ghrp_post_title filter — full programmatic override of the final post title (after format prefixing).
• Title prompt guidance is now project-neutral (was implicitly plugin-centric).

Help & docs

• Repositories help tab: per-repo options list now covers Author, Post Status, Categories, Tags, Featured Image, and Paused.
• AI & Prompts help tab: new "Post Titles" subsection.
• Long filter names in help tabs wrapped in <code> to fix a horizontal scroll bar in narrow help panels.

Upgrade

No data migration required. Existing sites continue to use the Plugin name and version title format unless you change the new setting.

v0.9.2

Bug fix

Surfaces a top-of-page warning when no AI connector is configured.

What changed

• New Settings_Page::is_any_connector_configured() static helper queries the WordPress AI Client registry directly (no caching).
• The plugin admin page renders a notice notice-warning at the top of both tabs (Repositories and Settings) when no provider is configured and ready. Previously the warning lived inside the Settings tab's AI Connector status field and was cached for up to a minute.
• Notice updates immediately when you toggle connectors in Settings → Connectors.

v0.9.1

Bug fix

Plugin now fails gracefully when the WordPress AI Client API isn't available, instead of fataling.

What changed

• Compatibility check uses function_exists('wp_ai_client_prompt') (the actual signal that matters) plus a PHP ≥ 8.2 check.
• Composer autoloader now loads after the compatibility check, so the plugin file does the bare minimum on incompatible environments.
• On incompatible installs, an admin notice explains the requirement and the plugin remains inert.
• Compatible with WordPress 7.0 prereleases (beta / RC) — the check no longer rejects version strings like 7.0-RC1.

v0.9.0 — Renamed to GitHub Release Posts

What's new

This is a rename + rebrand release. The plugin's public identity now matches its name (GitHub Release Posts) ahead of WordPress.org submission. No new functionality.

What changed

• Folder + main file: changelog-to-blog-post/ → github-release-posts/
• Text domain: changelog-to-blog-post → github-release-posts
• PHP namespace: TenUp\ChangelogToBlogPost → Jakemgold\GitHubReleasePosts
• Hooks / options / transients: ctbp_* → ghrp_*
• CSS / JS class prefix: ctbp- → ghrp-
• REST namespace: ctbp/v1 → ghrp/v1
• Constants: CHANGELOG_TO_BLOG_POST_* → GITHUB_RELEASE_POSTS_*
• Composer package: 10up/changelog-to-blog-post → jakemgold/github-release-posts

Filter / hook renames

All filters keep the same arguments and behavior, only the prefix changed:

ctbp_default_post_status        → ghrp_default_post_status
ctbp_default_categories         → ghrp_default_categories
ctbp_default_tags               → ghrp_default_tags
ctbp_post_status                → ghrp_post_status
ctbp_post_terms                 → ghrp_post_terms
ctbp_post_featured_image        → ghrp_post_featured_image
ctbp_ai_disclosure_text         → ghrp_ai_disclosure_text
ctbp_max_release_body_length    → ghrp_max_release_body_length
ctbp_sideload_allowed_domains   → ghrp_sideload_allowed_domains
ctbp_check_frequency            → ghrp_check_frequency
ctbp_register_ai_providers      → ghrp_register_ai_providers
ctbp_wp_ai_client_model_preferences → ghrp_wp_ai_client_model_preferences
ctbp_openai_reasoning_effort    → ghrp_openai_reasoning_effort
ctbp_research_depth             → ghrp_research_depth
ctbp_generate_prompt            → ghrp_generate_prompt
ctbp_prompt_title_guidance      → ghrp_prompt_title_guidance
ctbp_prompt_content_guidance    → ghrp_prompt_content_guidance
ctbp_release_body               → ghrp_release_body

Upgrading from 0.8.x

There is no automatic migration. This is a pre-release plugin with no expected install base — uninstall the old plugin and install fresh.

v0.8.1

What's new

This release adds an optional Deep research mode that gives the AI more context when generating posts, plus minor settings UI polish.

Deep research depth

• New Research Depth setting in the Post Creation section: choose Standard or Deep.
• Standard (default) — the AI reviews the release notes, linked issues and PRs, repository metadata, and the README.
• Deep — additionally fetches commit messages and a file-change summary between the previous and current release tag via the GitHub Compare API. Useful when release notes are sparse, but uses more API tokens and generation time.
• Per-repo override available via the new ctbp_research_depth filter.

Settings UI polish

• Post Audience changed from a dropdown to radio buttons — clearer scanning of the descriptive options.
• The Post Creation section now renders before GitHub on the Settings tab.
• Cleaner page header copy on Tools → Release Posts.

Documentation

• Readme phrasing updated — describes researching each release, not just reading release notes.

v0.8.0

What's new

This release requires WordPress 7.0+ and uses the native WordPress Connectors API as the sole AI provider — replacing the previous direct OpenAI and Anthropic connectors.

Connectors integration

• AI generation via WordPress Connectors — works with Anthropic, OpenAI, Google, and any configured connector
• Preferred model list with automatic fallback: Claude Opus 4.7, GPT-5.5, Gemini 2.5 Pro
• OpenAI reasoning effort set to "high" automatically when OpenAI is the active provider
• Connector status panel in Settings replaces manual provider/API key configuration
• Two-tier warnings: guidance for wrong connector vs. right connector with non-preferred model

Improved notifications

• Contextual subject lines: "Gutenberg 19.0 — draft ready for review" instead of generic subjects
• AI-generated post titles shown in email body
• Actionable CTAs: "Review draft" for drafts, "View post" for published
• Intro paragraph with linked site URL and plugin attribution
• Send Test Email button in Notifications settings

Bug fixes

• Fixed adjacent <figure> placeholders not restoring in block content (caused CTBP_FIGURE_N visible in posts)
• Fixed error messages not visible on Generate button (now shown as tooltip)
• Fixed GitHub column overflow on narrow browsers
• Fixed all WPCS violations

Breaking changes

• Requires WordPress 7.0 or later (Connectors API)
• Removed direct OpenAI and Anthropic API key connectors
• Removed ctbp_openai_model and ctbp_anthropic_model filters (use ctbp_wp_ai_client_model_preferences instead)
• Removed test-connection REST endpoint

Thanks to @dkotter for helping prep these changes.