You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-46Lines changed: 2 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ Moreover, even if a plugin is closed, its existing versions are still downloadab
107
107
}
108
108
```
109
109
110
-
To catch these closed plugins, `WP Org Closed Plugin` queries [WordPress.org API](https://codex.wordpress.org/WordPress.org_API#Plugins) to check whether a plugin is closed and mark them as abandoned in Composer.
110
+
To catch these closed plugins, `WP Org Closed Plugin` queries [wp-packages.org](https://wp-packages.org/) for the list of plugins closed on WordPress.org and marks them as abandoned in Composer.
111
111
112
112
## What to do when a plugin is closed?
113
113
@@ -153,58 +153,14 @@ You should run `composer audit` without `--locked` to check for closed plugins.
153
153
154
154
### Cache
155
155
156
-
WordPress.org API responses are cached for 10 minutes.
156
+
The list of closed plugins is fetched from [wp-packages.org](https://wp-packages.org/) in a single request and cached for 10 minutes.
157
157
158
158
If you must clear the cache, delete the `<composer-cache-dir>/wp-org-closed-plugin` directory.
0 commit comments