Auto Release Posts for GitHub
Auto Release Posts for GitHub monitors GitHub repositories for new releases and uses AI to research each release and generate a human-readable blog post about it. Posts can be automatically published or held as drafts…
Use with caution
Auto Release Posts for GitHub works, but test it on a staging site before relying on it in 2026. Is rated 5/5 and was last updated 3 months ago, and scores 51/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
- Needs PHP 8.2 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Auto Release Posts for GitH… stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| AI | >100 |
| automation | >100 |
| blog post | >100 |
| Github | >100 |
| releases | >100 |
Rating breakdown
★★★★★★★★★★ 5 from 2 reviews
About Auto Release Posts for GitHub
From the official readme · v1.2.0Description
Auto Release Posts for GitHub monitors GitHub repositories for new releases and uses AI to research each release and generate a human-readable blog post about it. Posts can be automatically published or held as drafts for review, with email notifications when new posts are ready.
Built on the AI Client API and Connectors introduced in WordPress 7.0 — configure your AI provider (Anthropic, OpenAI, Google, or any other connector) once under Settings → Connectors, and this plugin uses whatever you’ve set up. No AI API keys to manage in the plugin itself.
How it works:
- Monitor — Add any GitHub repository and the plugin checks for new releases daily via WP-Cron.
- Generate — When a new release is detected, the AI researches the release and writes a blog post tailored to your audience.
- Publish — Posts are created as drafts for review, or published automatically based on your per-repository settings.
You can also generate a post on demand at any time from the Repositories tab.
Features:
- Monitor multiple GitHub repositories for new releases
- AI-powered post generation via WordPress Connectors — works with Anthropic, OpenAI, Google, and any other configured connector
- Significance-aware content — patch, minor, major, and security releases get tailored tone and structure
- Choose the research depth — Standard reviews release notes, linked issues and PRs, metadata, and the README; Deep adds commit messages and file changes since the last release
- SEO-friendly post slugs and excerpts generated automatically by AI
- Configurable publish/draft workflow with per-repository overrides
- Per-repository post defaults (categories, tags, post status)
- Choose your post title format — prefix with project name and version, version only, or no auto-prefix (let the AI write the full title in single-project sites)
- Generate posts on demand for any historical release — pick from a version dropdown when a repo has multiple releases; older releases are automatically backdated to keep the archive in chronological order
- Custom prompt instructions to guide AI writing style, tone, and voice
- Regenerate posts with feedback — refine AI output directly from the block editor sidebar
- Email notifications on draft creation, publication, or both
- Source attribution in the block editor — see which GitHub release generated each post
- Idempotency — the same release never creates duplicate posts
- Optional project link support — enter a URL or WordPress.org slug for download CTAs
- Optional pre-release tracking per repository — track stable releases by default, or opt in to include betas, release candidates, and other pre-release versions
- Monorepo support — per-repository tag patterns limit posts to selected packages (e.g.
@headstartwp/core@*, @headstartwp/next@*) when one repository releases many packages
For developers:
- Extensible via filter hooks at every stage of the pipeline
- Customize preferred AI models via the
ghrp_wp_ai_client_model_preferencesfilter - Override significance classification, prompt content, post terms, and post status per-release
- All prompt templates defined in code, versioned with the plugin
Requirements:
- WordPress 7.0 or later
- PHP 8.2 or later
- At least one AI connector configured under Settings → Connectors (Anthropic, OpenAI, or Google recommended)
Auto Release Posts for GitHub is an independent project. It is not affiliated with, endorsed by, or sponsored by GitHub, Inc. or the WordPress Foundation. “GitHub” and “WordPress” are used here for descriptive purposes only.
External Services
This plugin connects to external services to fetch release data and (via WordPress Connectors) generate post content. Each service is described below.
GitHub REST API
- What it is: GitHub’s REST API (
https://api.github.com) is used to read release data and repository metadata, and — when a Personal Access Token is configured — to list repositories the token can access. - What is sent: HTTP requests to
api.github.comcontaining the repository owner and name. If a GitHub Personal Access Token is configured (in the Settings tab, or via theGHRP_PATconstant or environment variable), the token is sent in the Authorization header. - When it is sent: Daily via WP-Cron (configurable via the
ghrp_check_frequencyfilter), and on demand when generating, regenerating, or refreshing posts from the plugin’s admin screens. - Terms of Service: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
- Privacy Policy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement
Image sideloading from GitHub-hosted domains
- What it is: When AI-generated post content references images hosted on
github.com,githubusercontent.com, orgithub.io, the plugin downloads those images to the WordPress Media Library so posts render without external image dependencies. - What is sent: HTTP GET requests to the specific image URLs referenced by the AI output. No data beyond a standard HTTP request.
- When it is sent: At post creation or regeneration time, for image URLs included in the AI-generated content. The allowed domains and limits are configurable via the
ghrp_sideload_allowed_domains,ghrp_max_sideload_images,ghrp_sideload_time_budget, and related filters. - Terms of Service and Privacy Policy: same as GitHub above.
AI providers (via WordPress Connectors)
- What it is: AI-generated post content is produced by whichever AI connector you have configured under Settings → Connectors in WordPress 7.0+. The plugin does not call AI provider APIs directly — it dispatches prompts through the WordPress AI Client API.
- What is sent: The release title, release notes body, repository metadata (owner/name, language, description), and any custom prompt instructions you have configured are sent to the AI provider selected by your connector. Optional Deep research mode additionally sends recent commit messages and file change summaries between releases.
- When it is sent: When a new release is detected by the daily scheduled check, when you click “Generate post” or “Regenerate,” and when regenerating from the block editor sidebar.
Privacy and terms for the AI provider depend on which connector is configured. Common providers:
Source Code
The complete, human-readable source code for this plugin is published at:
https://github.com/jakemgold/github-release-posts-wordpress
Bundled JavaScript. The minified files under dist/js/ are built from the source files under assets/js/ using the @10up/scripts toolkit (which wraps Webpack). To rebuild:
npm install && npm run build
Source-to-build mapping:
dist/js/admin.jsis built fromassets/js/admin/index.jsdist/js/editor.jsis built fromassets/js/editor/index.jsdist/css/admin-style.cssis built fromassets/css/admin/style.css
Both source and build outputs ship with the plugin, so the source is available locally as well as in the public repository.
Third-party libraries. The plugin has no third-party PHP dependencies. The vendor/ directory only contains Composer’s own PSR-4 autoloader scaffolding generated from the plugin’s own classes — it does not include any external libraries. The composer.json require block requires only php: >=8.2. PAT encryption uses libsodium, which has been part of PHP core since 7.2.
Bundled npm packages used at build time (development only — not shipped at runtime): @10up/scripts (which itself bundles Webpack, ESLint, Babel, and the build-time-only wp-prettier and eslint-plugin-jsdoc overrides). All declared in package.json and package-lock.json. None of these end up in the distributed plugin.
Installation
- Upload the plugin files to
/wp-content/plugins/auto-release-posts-for-github/, or install via the WordPress Plugins screen. - Activate the plugin through the Plugins screen in WordPress.
- Go to Tools → Release Posts to configure your AI provider and add repositories.
Frequently asked questions
Which AI providers are supported?
The plugin uses WordPress Connectors (built into WordPress 7.0+) to communicate with AI providers. Any connector installed on your site will work. We recommend Anthropic (Claude Opus 4.7), OpenAI (GPT-5.5), or Google (Gemini 2.5 Pro) for best results. Configure your connector under Settings → Connectors.
Do I need a GitHub API key?
No. The plugin uses the public GitHub API for public repositories. Adding an optional Personal Access Token raises the API rate limit from 60 to 5,000 requests per hour and replaces the “owner/repo” text field on the Repositories tab with a dropdown of repos the token can access.
Does it work with private repositories?
Yes. Add a GitHub Personal Access Token in the Settings tab. A fine-grained token scoped to the specific repositories you want to monitor is recommended; a classic token with the repo scope also works.
How often does the plugin check for new releases?
By default, the plugin checks daily via WP-Cron. Developers can change this to hourly, twice daily, or weekly using the ghrp_check_frequency filter.
Can I customize the AI-generated content?
Yes, in two ways. Site owners can enter custom prompt instructions in the Settings tab to guide the AI’s writing style, tone, and voice. Developers can use filter hooks (ghrp_prompt, ghrp_prompt_title_guidance, ghrp_prompt_content_guidance) for full control over the prompt sent to the AI.
Can I edit or regenerate a post after it’s created?
Yes. Generated posts are standard WordPress posts and can be edited normally in the block editor. A Release Attribution panel in the editor sidebar lets you regenerate the content with optional feedback — for example, “make it shorter” or “emphasize the security fix.”
What shows up in the block editor for generated posts?
A Release Attribution panel appears in the document sidebar, showing which GitHub release the post was generated from with a link to the release notes. From this panel you can also regenerate the post content with feedback.
Changelog
1.2.0
- Monorepo support for GitHub repositories that release multiple packages. Edit the repository settings in WordPress for detected monorepos to choose which packages get posts. Developers can customize the release tag patterns the plugin uses with the
ghrp_repo_tag_patternsfilter. Full details in the Help tab on the Release Posts admin screen. - The repository table’s generate button is now labeled “Generate draft” and the version picker explains that manually generated posts are always drafts for review, clarifying that the Status setting applies to posts created by the scheduled check.
- Adding a repository now verifies it exists on GitHub, so a mistyped path is rejected with a helpful message instead of being silently tracked forever.
1.1.2
- The Settings page now warns clearly when GitHub tokens cannot be stored because the site’s
AUTH_KEYsecurity constant is missing or still set to its placeholder — with an inline warning on the token field itself, and an error notice when a save fails. Previously the page reported “Settings saved.” while the token was silently not stored.
1.1.1
A small bugfix release — no configuration changes required.
- Fixed a parsing issue where an AI response with a blank line after the title could save the post’s URL keywords as the visible excerpt, drop them from the post slug, and leak the intended excerpt into the top of the post body. Regenerating an affected post corrects it.
- On multisite, network super admins who are members of a site can now be selected as a repository’s post author. Previously they were missing from the author dropdown (WordPress capability queries can’t see super admins), and editing such a repository could silently reassign its author. A new
ghrp_author_dropdown_user_idsfilter allows further customization of the selectable authors.
1.1.0
A reliability, security, and model-routing release. Your existing repositories and generated posts are unaffected, and no configuration changes are required.
New: automatic model selection
- The plugin now routes each AI provider to its newest flagship model automatically — the latest Claude Opus, the latest GPT, and the latest stable Gemini Pro — resolved from your connected provider and cached for a week. It stays current as providers release new models, without waiting for a plugin update. You can still pin specific models with the
ghrp_wp_ai_client_model_preferencesfilter.
Reliability
- AI provider errors (timeouts, quota, or rate limits) are now recorded and reported instead of silently aborting the rest of a scheduled run and skipping the failure-notification email.
- A GitHub response that succeeds while consuming your last API request of the hour is no longer discarded as “rate limited,” so a just-published release is no longer skipped until the next run.
- Overlapping scheduled runs can no longer produce duplicate posts or double-charge AI usage.
- With pre-releases enabled, the newest release is now chosen by version number rather than publish date, so a back-ported patch to an older version can’t hide the genuinely latest release.
- Post generation now reports a real failure instead of a false “published” when the post status couldn’t be applied, and the “releases skipped due to errors” admin notice now actually appears when relevant.
- Editing a release’s notes now regenerates the post instead of returning a stale cached version, and a rare caching collision that could mix two repositories’ content has been fixed.
- The Repositories screen’s “Last Post” column now shows the correct latest post for every repository, even when one repository has many posts.
- If your GitHub token can’t be encrypted (for example, a missing WordPress
AUTH_KEY), the settings page now shows an error instead of silently saving an empty token. - The Settings screen’s “AI Connector” status now names the provider and model a post will actually be generated with (following the Claude → OpenAI → Google preference order) and updates immediately when you activate or deactivate a connector; previously it could show a different provider and model than the one used, or lag behind a connector change. Relatedly, OpenAI’s reasoning-effort setting is now applied whenever OpenAI is the active provider, even when a Google connector is also configured, and that effort level is shown in the status line (e.g. “gpt-5.5, high reasoning effort”).
Security hardening
- Image sideloading now re-checks the destination host on every redirect, closing a server-side request path where an allowed GitHub Pages URL could redirect a download to an internal address.
- References to issues and pull requests in release notes can no longer steer the site’s GitHub token to unintended API endpoints, and repository identifiers containing path-traversal segments are now rejected.
- Captions and titles derived from AI or release content are sanitized before saving, README heading extraction is length-bounded, and release-note truncation is now multibyte-safe.
- The stored GitHub token is no longer erased when the token is supplied via a
wp-config.phpconstant and the settings page is saved, and the plugin’s authenticated GitHub requests no longer follow redirects (so the token can’t be replayed to another host).
Other fixes
- Email notifications now include a plain-text alternative for better deliverability and no longer list the same post twice.
- Very large or malformed AI output can no longer result in a blank post body.
- GitHub image URLs with mixed-case hosts are now sideloaded correctly, and a configured featured image is validated before it is applied.
1.0.3
- Fixed an issue where inline editing of repository settings failed to open when one or more categories were assigned.
- Fixed an issue where adding tags to a repository failed to save. New tags are now created automatically if they don’t already exist.
- Fixed the link in the post-generation admin notice not opening the newly created draft or post.
- Uninstalling the plugin now preserves your repository configuration and keeps previously generated posts linked to their releases, so reinstalling no longer requires re-entering your repositories or risks creating duplicate posts. All other plugin settings, caches, and scheduled tasks are still removed.
1.0.2
Addresses WordPress.org reviewer feedback on prefix consistency.
- Renamed plugin constants
GITHUB_RELEASE_POSTS_VERSION,_URL,_PATH,_INCtoGHRP_VERSION,GHRP_URL,GHRP_PATH,GHRP_INCfor prefix consistency. - Renamed the GitHub PAT environment variable / PHP constant from
GITHUB_RELEASE_POSTS_PATtoGHRP_PAT. Sites that supplied the token viawp-config.phpor an environment variable must update the constant/var name. - Renamed the admin JavaScript global from
ctbpAdmin/ctbpFetchtoghrpAdmin/ghrpFetch, completing the v0.9.0 rebrand. Removed remaining[CTBP]debug-log prefixes and internal placeholder markers from the v0.9.0 era.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Auto Release Posts for GitHub alternatives
All AI plugins →
FAQ
Auto Release Posts for GitHub: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 14, 2026
Is Auto Release Posts for GitHub free?
Yes. Auto Release Posts for GitHub is free to download and use from the official WordPress.org plugin directory.
Is Auto Release Posts for GitHub safe to use in 2026?
Auto Release Posts for GitHub works, but test it on a staging site before relying on it in 2026. Is rated 5/5 and was last updated 3 months ago, and scores 51/100 on our health check.
How many websites use Auto Release Posts for GitHub?
Auto Release Posts for GitHub is active on <10 WordPress websites and has been downloaded 985 times since it launched in June 2026. It was downloaded 145 times in the last 30 days.
Does Auto Release Posts for GitHub work with WordPress 7.1?
Auto Release Posts for GitHub is officially tested up to WordPress 7.0.7, while the latest release is 7.1.3. It may still work, but try it on a staging site first.
What PHP version does Auto Release Posts for GitHub need?
Auto Release Posts for GitHub requires PHP 8.2 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Auto Release Posts for GitHub last updated?
The latest version, 1.2.0, was released on July 21, 2026 (3 months ago).
Who makes Auto Release Posts for GitHub?
Auto Release Posts for GitHub is developed and maintained by Jake Goldman.
What are the best alternatives to Auto Release Posts for GitHub?
The most popular alternatives to Auto Release Posts for GitHub are Elementor Website Builder (10M+ installs), All in One SEO (2M+ installs) and AI Agent by SiteGround (1M+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
