v0.5.0
This commit is contained in:
parent
38fbcf80a5
commit
90ac22a845
8 changed files with 379 additions and 5 deletions
|
|
@ -1,5 +1,28 @@
|
|||
== Changelog ==
|
||||
|
||||
= 0.5.0 =
|
||||
|
||||
_Release date: 2026-08-14_
|
||||
|
||||
**Highlights**
|
||||
|
||||
* Native WordPress update integration: installed catalog plugins feed into WordPress's own update system. The standard "Update available" badge appears on the Plugins screen, and clicking "Update now" runs the normal WordPress updater with the ROBOTSTXT store as the download source — no custom UI.
|
||||
|
||||
**Added**
|
||||
|
||||
* `Robotstxt_Manager_Updater` — injects catalog update data into the `update_plugins` transient (`pre_set_site_transient_update_plugins`): a `response` entry for outdated catalog plugins (package = the store's download proxy; premium entries append the account API key as `api_key`, which Core 1.5.0+ accepts as a query parameter because the native upgrader cannot send headers) and a `no_update` entry for up-to-date ones. Entries injected by a plugin's own bundled SDK are never overwritten.
|
||||
* `plugins_api` filter — the "View details" modal for catalog slugs is served from catalog data (name, version, requires, tested, homepage, description section, icon, banner).
|
||||
* "Refresh catalog" now also deletes the `update_plugins` transient so the update badges re-evaluate immediately.
|
||||
|
||||
**Changed**
|
||||
|
||||
* Plugin version 0.4.0 → 0.5.0. No database schema changes (no custom tables).
|
||||
|
||||
**Compatibility**
|
||||
|
||||
* WordPress: 7.0 - 7.1 (declared floor of the ecosystem; scan-confirmed lower)
|
||||
* PHP: 8.4 - 8.5 (declared floor of the ecosystem; scan-confirmed lower)
|
||||
|
||||
= 0.4.0 =
|
||||
|
||||
_Release date: 2026-08-14_
|
||||
|
|
|
|||
Loading…
Reference in a new issue