Unsupervised/unsupervised-scheduler
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 12 Wiki Activity
137 Commits 2 Branches 12 Tags
fae1fd08ba973176e40cb5db2dc1f047a679df1d
Commit Graph
3 Commits
Author SHA1 Message Date
thatguygriffandClaude Opus 4.8 51dd032668 Show the Enable auto-updates toggle for the self-updater
CI / Tests (PHP 8.1) (pull_request) Successful in 47s
Details
CI / Tests (PHP 8.2) (pull_request) Successful in 47s
Details
CI / No Debug Code (pull_request) Successful in 3s
Details
CI / Coding Standards (pull_request) Successful in 3m7s
Details
CI / Tests (PHP 8.3) (pull_request) Successful in 2m38s
Details
CI / PHPStan (pull_request) Successful in 2m50s
Details
CI / Build Plugin Zip (pull_request) Skipped
Details 
WordPress only renders the "Enable auto-updates" toggle for a plugin that
appears in the update_plugins transient's response or no_update list, which
is what sets core's update-supported flag. UpdateChecker only populated the
response side (when a newer release existed), so between releases the plugin
was absent from the transient and the toggle never showed.

provideUpdate() now returns a no_update payload (installed version, empty
package) whenever no newer release is offered — including when the release
lookup fails — so the plugin stays in the transient and the toggle appears.
The response path (one-click and unattended updates) is unchanged.

Bumps to 1.1.1 so the fix ships to installed sites via the self-updater.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
 2026-07-24 08:46:31 -03:00
thatguygriffandClaude Opus 4.8 83be388186 Point plugin metadata links at Unsupervised and Gitea
CI / No Debug Code (pull_request) Successful in 4s
Details
CI / Tests (PHP 8.2) (pull_request) Successful in 39s
Details
CI / Tests (PHP 8.1) (pull_request) Successful in 1m21s
Details
CI / Coding Standards (pull_request) Successful in 2m52s
Details
CI / PHPStan (pull_request) Successful in 2m53s
Details
CI / Tests (PHP 8.3) (pull_request) Successful in 2m36s
Details
CI / Build Plugin Zip (pull_request) Skipped
Details 
Make the "By Unsupervised" author link go to https://unsupervised.ca
(via a new Author URI header) and the plugin site / "View details" link
point at the Gitea project instead of WordPress.org.

Core's "View details" link opened a thickbox iframe against the
WordPress.org plugin-information API, which 404s ("Plugin not found")
for this off-directory plugin. A plugin_row_meta filter now replaces it
with a new-tab link to the matching Gitea release tag page; embedding
Gitea in the iframe is blocked by its X-Frame-Options anyway.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
 2026-07-23 11:14:44 -03:00
thatguygriffandClaude Fable 5 ab055c7a0c Serve plugin updates from tagged Gitea releases
CI / Tests (PHP 8.1) (pull_request) Successful in 45s
Details
CI / Tests (PHP 8.2) (pull_request) Successful in 44s
Details
CI / No Debug Code (pull_request) Successful in 2s
Details
CI / Coding Standards (pull_request) Successful in 2m43s
Details
CI / PHPStan (pull_request) Successful in 2m51s
Details
CI / Tests (PHP 8.3) (pull_request) Successful in 2m34s
Details
CI / Build Plugin Zip (pull_request) Skipped
Details 
Closes #65

Declare an Update URI header and answer core's update_plugins_{hostname}
filter from a new Update\UpdateChecker that offers the latest published
Gitea release's zip asset when it is newer than the installed version,
with transient caching and silent degradation on API failures.

Add a release workflow that fires on v* tag pushes: verifies the tag
matches the plugin Version header, runs the tests, builds the plugin zip,
and attaches it to the release (reusing a UI-created release, flagging
hyphenated versions as pre-release so /releases/latest skips them).

Co-Authored-By: Claude Fable 5 <[email protected]>
 2026-07-18 11:09:50 -03:00