WP Manifestindependent plugin directory
manifest / updates / alynt-plugin-updater

Alynt Plugin Updater WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

A lightweight WordPress plugin that enables automatic updates for GitHub-hosted plugins. Works like Git Updater but focused on simplicity — GitHub public repositories only, using WordPress's native update system.

★ 0stars
33release downloads
v1.1.5latest · 3mo ago

Install

Download alynt-plugin-updater-v1.1.5.zip From the v1.1.5 release on GitHub, Jul 18, 2026

Upload it under Plugins → Add New Plugin → Upload Plugin, then activate.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/nichlasb/alynt-plugin-updater/releases/download/v1.1.5/alynt-plugin-updater-v1.1.5.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.

A lightweight WordPress plugin that enables automatic updates for GitHub-hosted plugins. Uses WordPress's native update system with GitHub public releases.

Features

  • Checks GitHub releases for new versions
  • Supports tags formatted as v1.0.0 or 1.0.0
  • Automatic fallback to tags API when releases are unavailable
  • Per-plugin "Check for updates" link in the plugins list
  • Optional GitHub webhook support for instant update checks
  • Settings page with status, cache controls, and webhook setup
  • Configurable check frequency (every 6, 12, 24 hours, or weekly)
  • GitHub API rate limit tracking and handling
  • Comprehensive caching system to minimize API requests
  • Preserves managed plugins' active state and active-list order during programmatic updates

Requirements

  • WordPress 6.0 or higher
  • PHP 7.4 or higher
  • Composer (for development)
  • Node.js 14+ and npm (for asset building)

Installation

  1. Upload the alynt-plugin-updater folder to /wp-content/plugins/.
  2. Activate the plugin via the WordPress admin.
  3. Visit Settings → Plugin Updater to configure options.

Registering a Plugin

Add a header to the plugin's main file:

GitHub Plugin URI: username/repository

Or use the full URL:

GitHub Plugin URI: https://github.com/username/repository

Webhook Setup (Optional)

Webhook support is optional but provides instant update notifications. Configure it in Settings → Plugin Updater and follow the instructions shown.

  1. Go to your GitHub repository → Settings → Webhooks → Add webhook
  2. Set Payload URL to the webhook URL shown in plugin settings
  3. Set Content type to application/json
  4. Set Secret to the secret key shown in plugin settings
  5. Enable SSL verification
  6. Select individual events → Check Releases only
  7. Click Add webhook

Note: Even without webhooks, the plugin will check for updates via scheduled cron jobs.

Development

Install dependencies:

composer install
npm install

Build assets:

npm run build

Lint JavaScript:

npm run lint

Run tests:

composer test

Check code style:

composer phpcs

FAQ

How do I register a plugin for updates?

Add the following header to your plugin's main PHP file:

/**
 * GitHub Plugin URI: username/repository
 */

Or use the full URL:

/**
 * GitHub Plugin URI: https://github.com/username/repository
 */

Does this work with private repositories?

No, this plugin only supports public GitHub repositories. Private repository support would require GitHub authentication tokens.

How often does it check for updates?

By default, every 12 hours. You can configure this in Settings → Plugin Updater to check every 6 hours, 12 hours, 24 hours, or weekly.

Do I need to set up webhooks?

No, webhooks are optional. The plugin will check for updates via scheduled cron jobs even without webhooks. Webhooks simply provide instant notifications when you publish a new release.

What happens if GitHub rate limits are reached?

The plugin will use cached data until the rate limit resets. The settings page shows when the limit will reset. For unauthenticated requests, GitHub allows 60 requests per hour.

Can I manually check for updates?

Yes, there are two ways:

  1. Click the "Check for updates" link below any GitHub-managed plugin in the plugins list
  2. Use the "Check All Updates" button in Settings → Plugin Updater

What version tag formats are supported?

Both v1.0.0 and 1.0.0 formats are supported. The plugin automatically normalizes version strings.

Does this plugin modify my managed plugins?

No, it only provides update information to WordPress. The actual plugin updates are handled by WordPress's native update system.

Where can I find the plugin logs?

If WP_DEBUG is enabled, logs are written to your WordPress debug.log file with the prefix [Alynt Plugin Updater].

License

GPL v2 or later.

Releases

7 releases. Each count is every asset in that release; expand a row for the breakdown.

Tag
Published
Assets
Downloads
v1.1.5 latest
Jul 18, 2026 3mo ago
alynt-plugin-updater-v1.1.5.zip
17
Jul 18, 2026 3mo ago
alynt-plugin-updater-v1.1.4.zip
1
Jul 18, 2026 3mo ago
alynt-plugin-updater-v1.1.3.zip
2
Jul 17, 2026 3mo ago
alynt-plugin-updater-v1.1.2.zip
5
Mar 23, 2026 7mo ago
alynt-plugin-updater-v1.1.1.zip
6
Mar 20, 2026 7mo ago
alynt-plugin-updater-v1.1.0.zip
0
Jan 26, 2026 8mo ago
alynt-plugin-updater-v1.0.0.zip
2
A grade

Security

Alynt Plugin Updater 1.1.5 · audited by WP Registry

No security issues found.

Audited release
1.1.5
Findings
none
Worst severity
—
Content hash
660ece2ba1ce3430db0597bd…

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.