Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneesstack72

Relationships

#4935 Extension push: a registry 5xx reads as the user's fault and gives no next step

Opened by stack72 · 11/20/2026· Shipped 11/20/2026

What happens

When the swamp-club registry answers a 5xx during swamp extension push (dry run or real), the CLI prints three stacked error prefixes and the server's bare message:

Error: Registry check "version exists" could not run: registry lookup failed: Extension API error (HTTP 500): Internal server error

Seen by @bixu in swamp-club#4932: the message did not say the fault was on swamp-club rather than in their extension or CI, nor what to do next.

Expected

One sentence that says swamp-club failed (with the HTTP status and the failing URL), that the fault is not in the user's extension, and what to do: retry later, and report it with swamp issue bug if it keeps failing.

Where

The text is built in three layers: src/infrastructure/http/extension_api_client.ts (Extension API error), src/libswamp/extensions/push.ts (registry lookup failed), src/domain/extensions/extension_publish_checks.ts registryChecksVerdict (could not run). Only the message changes; exit behaviour and the json output's structure stay as they are.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 8 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/20/2026, 5:03:57 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack7211/20/2026, 12:48:43 PM

Sign in to post a ripple.