Skip to main content
← Back to list
01Issue
BugIn ProgressSwamp CLIPublic
Assigneeszack

Relationships

#4634 Upgrading an extension by name leaves its manifest dependencies at their old versions

Opened by zhann · 11/11/2026

What happens

Upgrading an extension by name never upgrades the extensions it lists under dependencies, and a manifest dependency cannot name a minimum version. So a newer extension can run against an older dependency it needs.

Seen with swamp 20261103.144051.0. @zhann/dhl-parcel depends on @zhann/parcel-report. Starting with both at 2026.11.09.1, and 2026.11.09.2 of both on the registry:

swamp extension pull @zhann/dhl-parcel --yes   → dhl-parcel 2026.11.09.2, parcel-report stays 2026.11.09.1
swamp extension update @zhann/dhl-parcel       → dhl-parcel 2026.11.09.2, parcel-report stays 2026.11.09.1
swamp extension update                         → both 2026.11.09.2

Without --yes, swamp extension pull @zhann/dhl-parcel stops at the overwrite prompt ("The following files already exist and will be overwritten"); non-interactively it exits with "stdin is not a terminal".

A fresh pull does resolve the dependency at its latest version, so only upgrades leave it behind.

Expected

One of:

  • pull / update <name> also bring each dependency up to at least the version the new release was published against (or to latest, as a fresh pull does), or
  • dependencies takes a minimum version (e.g. "@zhann/parcel-report@>=2026.11.09.2"), which pull and update honour.

Today swamp extension push --dry-run accepts "@zhann/parcel-report@2026.11.09.2" as an opaque string, and the publishing docs list dependencies as bare names only, so authors cannot tell whether a version there means anything.

Workaround

swamp extension update with no name, which the READMEs now point to.

02Bog Flow
✓OPEN✓TRIAGED◉IN PROGRESS○SHIPPED+ 1 MOREASSIGNED+ 8 MOREREVIEW+ 20 MORECODE_CONFORMANCE_REVIEW

In Progress

11/11/2026, 3:07:14 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
zack assigned zack11/11/2026, 2:56:48 PM

Sign in to post a ripple.