Skip to main content
← Back to list
01Issue
FeatureShippedSwamp Club
Assigneesstack72

Relationships

#426 Display extension deprecation state on swamp-club pages

Opened by stack72 · 5/23/2026· Shipped 5/27/2026

Problem

When an extension is deprecated (see companion issue #425 for the CLI side), swamp-club has no way to communicate this to users browsing the registry. Users may discover and start depending on a deprecated extension without realizing a better alternative exists.

Proposed Solution

Surface the deprecation state set by the CLI (swamp extension deprecate, tracked in #425) on swamp-club extension pages:

  1. Deprecation badge/icon — A visible indicator on the extension's page and in search results showing it is deprecated
  2. Deprecation notice — Display the author-provided reason text (e.g. "Merged into the collective extension")
  3. Successor link — If --superseded-by was provided, show a prominent link to the replacement extension's page (e.g. "Superseded by @bad-at-naming/libvirt")
  4. Search ranking — Deprecated extensions should be ranked lower in search results but still discoverable

Context

This is the swamp-club companion to #425 (CLI deprecation command). Together they provide the full deprecation lifecycle: the CLI sets the state, and swamp-club displays it.

The motivation comes from a real experience report where a user's fork became redundant after the upstream author incorporated changes, but there was no clean way to redirect users to the canonical extension.

Alternatives Considered

  • Hide deprecated extensions entirely: Too aggressive — they may still be in active use
  • Text-only notice without successor link: Misses the main value — telling users where to go next
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

5/27/2026, 3:01:44 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack725/27/2026, 2:08:24 PM

Sign in to post a ripple.