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
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,10 +73,10 @@ Package wpackagist-plugin/my-closed-plugin is abandoned because https://wordpres
73
73
74
74
## Why
75
75
76
-
When a plugin is closed on WordPress.org, [WPackagist](https://wpackagist.org/) not always remove it from its database immediately.
77
-
As a result, some closed plugins remain available for installation via WPackagist.
76
+
When a plugin is closed on WordPress.org, Composer repositories (e.g: [WPackagist](https://wpackagist.org/) & [WP Packages](https://wp-packages.org/) not always remove it from its database immediately.
77
+
Worse still, even after the Composer repositories removed it., a closed plugin might persists in `composer.lock` with references to download.wordPress.org endpoint and [WordPress plugin subversion repository](https://plugins.svn.wordpress.org/)
78
+
As a result, closed plugins remain installable.
78
79
79
-
Moreover, even if a plugin is closed, its existing versions are still downloadable from WordPress.org and the subversion repository.
80
80
```json
81
81
{
82
82
"repositories": [
@@ -87,7 +87,7 @@ Moreover, even if a plugin is closed, its existing versions are still downloadab
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.
110
+
To catch these closed plugins, `WP Org Closed Plugin` queries [WP Packages API](https://wp-packages.org/api/packages/wp-plugin/closed) 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
@@ -151,15 +151,15 @@ Skipped checking for closed plugins because of --locked.
151
151
152
152
You should run `composer audit` without `--locked` to check for closed plugins.
153
153
154
-
### Cache
155
-
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
-
158
-
If you must clear the cache, delete the `<composer-cache-dir>/wp-org-closed-plugin` directory.
0 commit comments