Skip to content

fix(admin): stop offering deprecated and known-broken plugins (#8246) - #8250

Merged
JohnMcLear merged 3 commits into
developfrom
fix/8246-catalog-deprecated
Sep 21, 2026
Merged

JohnMcLear merged 3 commits into
developfrom
fix/8246-catalog-deprecated

Conversation

@JohnMcLear

@JohnMcLear JohnMcLear commented Sep 20, 2026 •

Copy link
Copy Markdown
Member

Fixes #8246

What the feed actually provides

I fetched https://static.etherpad.org/plugins.json and inspected it before writing anything. Every one of the 174 entries has exactly these keys:

{"name": "ep_adminpads2", "description": "...", "time": "2025-01-06",
 "version": "2.1.110", "official": true, "downloads": 655,
 "compatibility": "compatible"}
  • No deprecation data, no compatibility range. There is nothing in the feed that says "npm deprecated this" or "works with Etherpad >= X".
  • There is a compatibility verdict — compatible (162), failed (10), warning (2) — produced by the registry's own compatibility run. Core ignored it completely until now. This is the second half of the issue's suggestion ("let the plugin feed carry a compatibility range") already available, with no feed change needed.
  • npm deprecation is real but currently empty for this feed. I queried registry.npmjs.org/<name>/latest for all 174 packages: zero are deprecated today. Notably ep_adminpads2 is not npm-deprecated either — it is archived on GitHub only. (ep_readonly_guest is deprecated on npm, and is already absent from the feed.)

So a deprecation-only filter, which is what the issue suggests, would be correct and future-proof but would not fix the reported case. That is why this PR combines three signals.

The fix

New pure module src/static/js/pluginfw/pluginCatalogFilter.ts decides, per entry, whether the catalog may offer it — cheapest signal first:

  1. feed compatibility === 'failed' → not offered (warning still is);
  2. supersededPlugins, a short hand-maintained map of packages that install cleanly and then break a working Etherpad. One entry today: ep_adminpads2, with the reason inline. Entries are explicitly meant to be retired once the package is deprecated on npm;
  3. deprecated on the published npm version metadata, looked up by installer.ts and passed in.

getAvailablePlugins() applies it after normalising the feed, so search, getAvailable and the "update available" check all inherit it.

Failure behaviour (point 3 of the brief): fail open, deliberately. The npm sweep is cached by name@version for 12 h, runs 8 requests at a time behind a single 15 s budget, and any package whose lookup fails — offline, npm firewalled, 404, timeout, budget exhausted — is listed, not hidden, with a log line. If the whole sweep throws, the feed-only signals still apply and everything else stays listed. An admin behind a firewall must get a working catalog, not an empty one; that would be a worse bug than the one being fixed. A plugin-feed failure still propagates as before (the admin UI shows its error) rather than silently rendering an empty catalog.

Install path: hiding a package from the listing does not stop a stale admin page, an older client or a replayed socket event from asking the server to install it, so install() applies the same policy. A superseded package is refused before any network call, so the block holds with npm unreachable; a package npm marks deprecated is refused from the preflight document the install already fetched for engines.node, i.e. no extra request. New error code PLUGIN_DEPRECATED with a localized toast. Fail-open still holds: if the registry cannot be reached the install proceeds, and pnpm run plugins i ep_<name> on the server goes through LinkInstaller directly, so an operator keeps an override. (Deprecated plugins are also never reported as updatable, so this cannot hijack the "update plugin" button.)

Concurrency: the admin page emits getInstalled and search together, and both reach getAvailablePlugins(). Concurrent callers share one in-flight refresh, and individual deprecation lookups share one in-flight request per name@version, so a cold load costs one feed fetch and one npm lookup per listed plugin — not two of each. The shared promise is cleared on failure, so a transient feed outage does not pin later callers to a rejected promise.

Installed plugins (point 4): hiding a plugin only stops new installs, so getInstalled now flags an already-installed deprecated/superseded plugin and the UI renders a localized DEPRECATED badge next to the version, with the upstream reason in the tooltip. getInstalled emits shallow copies rather than writing that status onto the live package objects in pluginDefs.plugins, so a badge cannot outlive its cause. Core (ep_etherpad-lite) is never looked up or flagged. New i18n keys admin_plugins.tag_deprecated, admin_plugins.deprecated_title and admin_plugins.install_error_deprecated (en + qqq).

Effect on the live catalog today

163 of 174 entries are still listed. The 11 hidden: ep_adminpads2 (superseded) plus the 10 the registry already marks failed — ep_back_button2, ep_content_title, ep_inline_toolbar_pro, ep_kaput, ep_mention, ep_mention_plugin, ep_mypads, ep_no_console, ep_script_elements, ep_script_page_view. Judgement call worth a second opinion: ep_mypads is in that list. Its npm build (2.0.1) does not support Etherpad 3.x, and Framasoft ships from framagit rather than npm, so hiding the npm build looks right — but say the word and I will restrict signal 1 or drop it.

Tests

  • src/tests/backend/specs/pluginCatalogFilter.ts — 19 cases pinning the decision table and the install-block policy, including "unknown deprecation state keeps the plugin", warning stays listed, and a missing compatibility field is not evidence of breakage.
  • src/tests/backend/specs/pluginCatalog.ts — 16 cases driving getAvailablePlugins() and install() with global.fetch stubbed: deprecated excluded / healthy still listed, ep_adminpads2 excluded, registry unreachable → full catalog still listed, npm 404 → still listed, feed 503 → still throws, one feed fetch + one npm lookup per plugin across two concurrent callers, a failed refresh does not stick, cache hit does not re-query, a failed lookup is not cached, install refused for superseded (with zero network calls) and for npm-deprecated.
  • src/tests/frontend-new/admin-spec/admin_plugin_catalog.spec.ts — chromium-admin: the catalog does not offer ep_adminpads2, and still offers ep_align.

Evidence: with the filter stubbed back out to pre-fix behaviour, 5 of the pluginCatalog.ts cases fail; with the fix, 35/35 pass across the two specs. Full backend suite 1735 passing, 0 failing; vitest 840 passed; pnpm run ts-check clean; admin tsc clean.

Real-UI verification

Server on :9160 with the built admin bundle, driven with Playwright:

catalog rows listed: 163
search "adminpads" -> ep_adminpads3 only          (ep_adminpads2 gone)
search "kaput"     -> []                          (compatibility: failed)
search "align"     -> ep_align                    (healthy plugin still offered)
installed rows:    ep_adminpads2 v2.1.110 DEPRECATED | ep_etherpad-lite CORE v3.3.5
badge tooltip:     "This plugin is no longer maintained and may break Etherpad.
                    Consider uninstalling it. Archived upstream and replaced by the
                    built-in Manage pads page. …"

The committed admin spec passes against that instance (2 passed), and so does the existing adminupdateplugins.spec.ts install/uninstall flow (3 passed) — a normal plugin still installs from the admin UI with the new install-time check in place.

Follow-up for a maintainer

The durable fix for ep_adminpads2 is npm deprecate ep_adminpads2 "archived; Etherpad's built-in Manage pads page replaces it" — signal 3 then catches it everywhere and the supersededPlugins entry can be deleted. I did not touch npm; that needs publish rights and your call.

Docs updated: PRIVACY.md (the npm registry lookups are now documented as a third outbound call, with how to switch them off), doc/plugins.md + doc/plugins.adoc, CHANGELOG.md.

🤖 Generated with Claude Code

https://claude.ai/code/session_013S4pYSjwUsiZtdtMMpW7bw

The admin "Available plugins" list was built straight from
`${updateServer}/plugins.json` with no filter, so every package the feed
knows about was installable from the admin UI — including packages that
are known not to work with the running Etherpad. The reported case is
`ep_adminpads2`: archived upstream, superseded by core's own Manage pads
page, and installing it breaks the admin UI because it registers
/admin/pads ahead of the core route and its template pulls scripts core
no longer ships.

The feed itself carries no deprecation data. It does carry a
`compatibility` verdict per plugin (`compatible` / `warning` / `failed`)
that core ignored until now. So three signals are combined, cheapest
first, in a new pure module `pluginCatalogFilter.ts`:

  1. feed `compatibility === 'failed'` — the plugin registry could not
     get the plugin working against current Etherpad;
  2. a short, documented list of superseded packages that install
     cleanly and then break a working install (currently only
     ep_adminpads2) — entries are meant to be retired once the package
     is deprecated on npm;
  3. `deprecated` on the published npm version metadata.

Signal 3 needs a registry lookup, so it is cached by name@version for
12 hours, runs 8 at a time behind a 15s overall budget, and is
fail-open: a package whose lookup fails (offline, npm firewalled, 404,
timeout) is listed, not hidden. Emptying the admin catalog because npm
was unreachable would be a worse bug than the one this fixes. The
install-time preflight already fetched the same npm document for
`engines.node`, so it now reads `deprecated` from it at no extra cost
and logs a warning; it does not block the install, because that same
code path serves the admin UI's "update plugin" button.

Hiding a plugin only stops new installs, so an already-installed plugin
that is deprecated or superseded is flagged with a "Deprecated" badge in
the Installed plugins list, with the upstream reason in its tooltip.
Core (ep_etherpad-lite) is never looked up or flagged.

Covered by backend specs for the decision table, the end-to-end catalog
path with a stubbed registry (deprecated excluded, healthy still listed,
registry failure still lists), and an admin Playwright spec that asserts
ep_adminpads2 is not offered while ep_align still is.

Fixes #8246

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013S4pYSjwUsiZtdtMMpW7bw
@qodo-code-review

Copy link
Copy Markdown

ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing

@qodo-free-for-open-source-projects

Copy link
Copy Markdown

PR Summary by Qodo

Filter deprecated and known-broken plugins from admin catalog

🐞 Bug fix 🧪 Tests 📝 Documentation 🕐 40+ Minutes

Grey Divider

AI Description

• Filters deprecated, incompatible, and superseded plugins from the admin catalog.
• Fails open with bounded, cached npm metadata checks.
• Flags installed problem plugins and documents and tests the new behavior.
Diagram

sequenceDiagram
  actor Admin
  participant UI as Admin UI
  participant API as Plugin API
  participant Feed as Plugin Feed
  participant NPM as npm Registry
  participant Filter as Catalog Filter
  Admin->>UI: Open plugin manager
  UI->>API: Request plugin data
  API->>Feed: Fetch catalog
  Feed-->>API: Entries and compatibility
  loop Uncached plugin versions
    API->>NPM: Fetch version metadata
    NPM-->>API: Deprecation status
  end
  API->>Filter: Apply safety signals
  Filter-->>API: Kept entries and warnings
  API-->>UI: Catalog and installed status
  UI-->>Admin: Safe catalog and badges
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Enrich the central plugin feed
  • ➕ Avoids per-instance npm request fan-out and associated privacy concerns.
  • ➕ Centralizes compatibility and deprecation policy in the plugin registry.
  • ➕ Produces faster, deterministic catalog responses for administrators.
  • ➖ Requires coordinated plugin-registry infrastructure changes.
  • ➖ Feed data can become stale between registry refreshes.
  • ➖ Does not immediately handle archived but non-deprecated packages such as ep_adminpads2.
2. Use feed compatibility only
  • ➕ Requires no additional outbound requests.
  • ➕ Uses an existing registry-generated compatibility verdict.
  • ➕ Has simpler caching and failure behavior.
  • ➖ Cannot identify npm-deprecated versions.
  • ➖ Does not catch compatible-looking packages that break core routes.
  • ➖ Would not resolve the reported ep_adminpads2 case without a separate override.

Recommendation: Use the PR's combined, fail-open approach for the immediate fix because it covers all currently available safety signals without making npm availability a catalog dependency. As a longer-term optimization, enrich the central plugin feed with exact-version deprecation data and retire local supersession entries after maintainers deprecate affected npm packages.

Files changed (16) +737 / -20

Enhancement (1) +2 / -0
en.jsonAdd English deprecated-plugin messages +2/-0

Add English deprecated-plugin messages

• Adds the installed-plugin badge label and explanatory warning tooltip.

src/locales/en.json

Bug fix (7) +329 / -19
index.cssStyle deprecated plugin badges +6/-0

Style deprecated plugin badges

• Adds warning-oriented colors and a help cursor for deprecated badges in the installed-plugin list.

admin/src/index.css

HomePage.tsxShow deprecation warnings for installed plugins +7/-0

Show deprecation warnings for installed plugins

• Renders a localized DEPRECATED badge when the server supplies a reason, exposing that reason in the tooltip.

admin/src/pages/HomePage.tsx

Plugin.tsExtend installed plugin data with deprecation reasons +7/-1

Extend installed plugin data with deprecation reasons

• Adds an optional server-provided deprecation or supersession reason to the installed-plugin model.

admin/src/pages/Plugin.ts

adminplugins.tsAttach warnings to installed plugin responses +18/-1

Attach warnings to installed plugin responses

• Checks installed plugins for npm deprecation or local supersession and attaches warning reasons. Lookup failures are logged without breaking the admin response.

src/node/hooks/express/adminplugins.ts

PackageInfo.tsModel compatibility and deprecation metadata +12/-1

Model compatibility and deprecation metadata

• Extends package information with feed compatibility verdicts and installed-plugin warning reasons.

src/node/types/PackageInfo.ts

installer.tsAdd bounded npm checks and catalog filtering +158/-16

Add bounded npm checks and catalog filtering

• Generalizes npm metadata fetching, adds a 12-hour exact-version deprecation cache with eight concurrent workers and a 15-second budget, and filters available plugins. It also warns about installed problem plugins while preserving fail-open behavior and existing engine checks.

src/static/js/pluginfw/installer.ts

pluginCatalogFilter.tsIntroduce pure plugin catalog safety rules +121/-0

Introduce pure plugin catalog safety rules

• Adds normalized npm deprecation handling and exclusion rules for deprecated, feed-failed, and locally superseded plugins. The initial supersession list blocks ep_adminpads2 with a documented reason.

src/static/js/pluginfw/pluginCatalogFilter.ts

Tests (3) +362 / -0
pluginCatalog.tsTest catalog integration and npm failure handling +195/-0

Test catalog integration and npm failure handling

• Covers exact-version lookups, exclusions, installed warnings, core exclusion, caching, retry after failures, unreachable npm, 404 responses, and plugin-feed errors with stubbed network calls.

src/tests/backend/specs/pluginCatalog.ts

pluginCatalogFilter.tsTest the catalog exclusion decision table +128/-0

Test the catalog exclusion decision table

• Pins normalization and filtering behavior for healthy, deprecated, superseded, failed, warning, missing, and malformed entries. It also verifies immutability and documented supersession reasons.

src/tests/backend/specs/pluginCatalogFilter.ts

admin_plugin_catalog.spec.tsVerify admin catalog hides broken plugins +39/-0

Verify admin catalog hides broken plugins

• Adds Playwright coverage confirming ep_adminpads2 is unavailable while a healthy plugin remains searchable.

src/tests/frontend-new/admin-spec/admin_plugin_catalog.spec.ts

Documentation (5) +44 / -1
CHANGELOG.mdDocument safer plugin catalog behavior +6/-0

Document safer plugin catalog behavior

• Adds a 3.3.7 notable fix describing catalog exclusions, installed-plugin warnings, and fail-open npm checks.

CHANGELOG.md

PRIVACY.mdDocument npm registry metadata requests +17/-1

Document npm registry metadata requests

• Documents the plugin manager's exact-version npm calls, cache frequency, payload, purpose, disablement path, and non-fatal failure behavior.

PRIVACY.md

plugins.adocExplain catalog filtering and manual overrides +10/-0

Explain catalog filtering and manual overrides

• Documents which plugins are excluded, how installed plugins are flagged, fail-open behavior, and continued CLI installation support.

doc/plugins.adoc

plugins.mdExplain catalog filtering and manual overrides +10/-0

Explain catalog filtering and manual overrides

• Documents which plugins are excluded, how installed plugins are flagged, fail-open behavior, and continued CLI installation support.

doc/plugins.md

qqq.jsonAdd translation guidance for deprecated label +1/-0

Add translation guidance for deprecated label

• Marks the new deprecated badge text as an identical translation term.

src/locales/qqq.json

@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Sep 20, 2026 •

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Grey Divider


Action required

1. Older clients install deprecated plugins ✓ Resolved 📎 Requirement gap ≡ Correctness
Description
install normalizes npm's deprecated field but only logs the resulting message before continuing
to linkInstaller.installPlugin(). A stale admin page or older client can therefore submit a
package that the refreshed catalog would hide, and the server still installs it.
Code

src/static/js/pluginfw/installer.ts[R265-268]

+    // The catalog does not offer deprecated plugins, but an install can still
+    // be requested by a stale admin page or by an older client. Installing is
+    // an explicit operator action so it is not blocked, only recorded.
+    const deprecation = normalizeDeprecation(meta?.deprecated);
Evidence
Compliance rule 1 treats permitting installation of deprecated plugins as failure. The changed
install preflight explicitly states that such installation is not blocked, and the implementation
only logs the deprecation before proceeding to the installer.

Exclude deprecated or incompatible plugins from the admin catalog
src/static/js/pluginfw/installer.ts[265-272]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The server-side install path only warns when npm marks a plugin deprecated, so stale or older admin clients can bypass the catalog filter and install it.
## Fix Focus Areas
- src/static/js/pluginfw/installer.ts[265-272]
## Recommended Fix
When `normalizeDeprecation(meta?.deprecated)` returns a message, reject the admin installation before calling `linkInstaller.installPlugin()`. Preserve any separate explicit command-line override outside this admin request path.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Opening the catalog floods npm ✓ Resolved 🐞 Bug ➹ Performance
Description
getAvailablePlugins() starts hideUninstallablePlugins() independently for every concurrent cache
miss, while fetchPluginDeprecations() caches only completed lookups and does not share in-flight
work. The admin page emits getInstalled and search together on initial load, so both paths can
sweep the entire catalog before either populates the cache, duplicating roughly one request per
listed plugin and increasing page latency and npm load.
Code

src/static/js/pluginfw/installer.ts[329]

+    deprecations = await fetchPluginDeprecations(list);
Evidence
The cache is checked before asynchronous requests begin but populated only after each lookup
finishes, and getAvailablePlugins() has no in-flight promise around its feed fetch and filtering.
The frontend emits getInstalled, whose update check loads the catalog, and search independently
during the same mount, allowing both handlers to observe an empty cache and launch complete sweeps.

src/static/js/pluginfw/installer.ts[212-253]
src/static/js/pluginfw/installer.ts[283-310]
src/node/hooks/express/adminplugins.ts[30-43]
admin/src/pages/HomePage.tsx[79-128]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Concurrent initial catalog requests independently fetch npm metadata for every plugin because neither `getAvailablePlugins()` nor the deprecation cache shares in-flight work. Opening the admin plugin page therefore creates duplicate full-catalog npm request bursts.
## Fix Focus Areas
- src/static/js/pluginfw/installer.ts[190-254]
- src/static/js/pluginfw/installer.ts[283-310]
- admin/src/pages/HomePage.tsx[79-128]
## Recommended Fix
Add a shared in-flight promise for catalog loading or per-`name@version` lookup promises, and have concurrent callers await that work. Clear the in-flight state in `finally` so failed requests can be retried while completed deprecation results continue using the existing TTL cache.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

3. Installed plugins keep obsolete warnings ✓ Resolved 🐞 Bug ≡ Correctness
Description
The getInstalled handler mutates package objects retained in pluginDefs.plugins and assigns
plugin.deprecated only when the latest warning map contains a truthy entry, without clearing
transient status fields first. When npm removes a deprecation, a lookup fails, or catalog checks are
disabled after a successful check, later socket responses reuse the retained value and the admin UI
renders the obsolete badge.
Code

src/node/hooks/express/adminplugins.ts[R71-73]

       plugin.updatable = updatable.includes(plugin.name);
+          const warning = deprecated.get(plugin.name);
+          if (warning) plugin.deprecated = warning;
Evidence
The handler builds the installed array from direct references to each
pluginDefs.plugins[plugin].package object, then conditionally adds deprecated without deleting
it when absent; because those objects remain in the plugin definitions, later requests begin with
state from earlier responses. The frontend renders any truthy deprecated string as a badge, and
disabling catalog access skips the refresh block entirely, allowing the retained value to continue
reaching the UI.

src/node/hooks/express/adminplugins.ts[43-45]
src/node/hooks/express/adminplugins.ts[61-76]
src/static/js/pluginfw/plugins.ts[128-150]
admin/src/pages/HomePage.tsx[247-256]
src/node/hooks/express/adminplugins.ts[55-74]
admin/src/pages/HomePage.tsx[250-256]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`getInstalled` writes transient warning and update fields onto package objects retained by `pluginDefs.plugins`, but does not remove them when a warning disappears, a lookup fails, or catalog checking is disabled. Ensure every installed-plugin response starts without stale `deprecated` or `updatable` values while preserving the package metadata required by the UI.
## Fix Focus Areas
- src/node/hooks/express/adminplugins.ts[55-74]
## Recommended Fix
Clone each package while constructing the `installed` array and apply current `deprecated` and `updatable` values only to those response-local objects. Alternatively, explicitly delete or reset both transient fields before applying the latest check results; in either case, ensure the catalog-disabled path also emits objects without stale status fields.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Tip of the day
💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment thread src/static/js/pluginfw/installer.ts Resolved
Comment thread src/static/js/pluginfw/installer.ts Resolved
Comment thread src/node/hooks/express/adminplugins.ts Resolved
Addresses the three findings from the Qodo review of #8250.

1. Refuse the install, not just the listing. Hiding a package from the
   catalog does not stop a stale admin page, an older client or a
   replayed socket event from asking the server to install it, so
   install() now applies the same policy: superseded packages are
   refused before any network call (so the block holds offline), and a
   package npm marks deprecated is refused after the preflight document
   it already fetches. An unreachable registry still lets the install
   proceed, and `pnpm run plugins i ep_<name>` goes through
   LinkInstaller directly, so an operator on the server can override.
   New error code PLUGIN_DEPRECATED, mapped to a localized toast.

2. Don't sweep npm twice on page load. The admin page emits
   `getInstalled` (which checks for updates) and `search` together, and
   both land in getAvailablePlugins(); on a cold cache each one fetched
   the feed and looked up every listed plugin. Concurrent callers now
   share one in-flight refresh, and individual deprecation lookups share
   one in-flight request per name@version. The shared promise is cleared
   on failure too, so a transient feed outage does not pin later callers
   to a rejected promise.

3. Don't leave a stale badge on an installed plugin. `getInstalled`
   wrote per-response status onto the live package objects held in
   pluginDefs.plugins, so a `deprecated` reason survived npm
   un-deprecating the package, a failed lookup, or the catalog being
   turned off. It now emits shallow copies and always assigns both
   status fields.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013S4pYSjwUsiZtdtMMpW7bw
CodeQL flags `url.includes('npmjs.org')` in the catalog spec as
incomplete URL sanitization (js/incomplete-url-substring-sanitization).
It is test-only routing, but the prefix match is both stricter and
clearer, so use it for the stub router and the call assertion.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013S4pYSjwUsiZtdtMMpW7bw
@JohnMcLear
JohnMcLear merged commit 30f643c into develop Sep 21, 2026
40 checks passed
@JohnMcLear
JohnMcLear deleted the fix/8246-catalog-deprecated branch September 21, 2026 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Admin plugin catalog lists deprecated and archived plugins

2 participants