Relationships
Blocked#730 extension pull serves a stale version that disagrees with search (honors a legacy per-extension serverUrl)
Opened by 4chems · 6/21/2026
Summary
swamp extension pull retrieves an OLD version of an extension even though swamp extension search (and the registry that push writes to) reports a newer one. It appears pull honors a stale per-extension serverUrl recorded in the repo's pin file.
Steps to reproduce
- An @collective extension was pinned long ago; its entry in
extensions/models/upstream_extensions.jsonhas"serverUrl": "https://swamp.club", while every other extension in the same file useshttps://swamp-club.com(looks like a registry rename swamp.club -> swamp-club.com left this pin on the legacy host). - Publish a new version of that extension:
swamp extension push manifest.yaml --yessucceeds. swamp extension search @collective/name --jsonnow reports"latestVersion": "<new>"with the new description. Good.swamp extension pull @collective/name(or...@<new>) -> the pulledmodels/*.tsandmanifest.yamlSTILL contain the OLD version's code/version string.- Deleting the extension's entry from
upstream_extensions.json(removing the pin) and re-pulling STILL serves the old version.
Also observed
- Pull logs:
Using cached bundle for "<model>.ts" — source may have changed but bundle could not be regenerated. - Clearing
.swamp/bundles/*/<model>.jsand.swamp/_extension_catalog.db*does not change the outcome.
Expected
pullshould fetch the version thatsearch/pushresolve to (or re-resolve the active registry when the pin is removed), and there should be a reliable way to force a fresh re-pull + bundle regeneration.
Impact
Any @collective/* extension whose pin still points at the legacy swamp.club host cannot be updated in a consuming repo after republish — the new version is silently ignored, with no error.
Environment
swamp 20260610.225536.0-sha.4559c368, macOS (darwin).
Closed
No activity in this phase yet.
stack72 commented 6/21/2026, 5:04:44 PM
Hey @4chems — thanks for the detailed report. We tried to reproduce this but couldn't: when we set a legacy serverUrl ("https://swamp.club") in the lockfile and re-pulled, the CLI correctly ignored it and fetched the latest version from swamp-club.com. The lockfile's serverUrl field is written but never read back for fetching — every pull path uses resolveServerUrl().
Could you share a bit more detail so we can pin this down?
- Which extension name and version are you seeing the mismatch on?
- After the pull, what does the manifest.yaml in .swamp/pulled-extensions// show for the version?
- What does the full pull log output show? (especially the "Pulling ...@..." line showing which version it resolves to)
- Is there a SWAMP_CLUB_URL env var set in your shell?
- What swamp version are you on? (swamp --version)
Sign in to post a ripple.