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

Relationships

#2050 Lab #2037 mitigation does not cover category-specific bundle stores (datastore-bundles, vault-bundles, report-bundles)

Opened by stack72 · 9/7/2026· Shipped 9/7/2026

Summary

The Lab #2037 auto-install bundle conflict mitigation (PR #2388) only covers .swamp/bundles/ (model extension bundles). Swamp maintains four parallel bundle stores:

  • .swamp/bundles/ — model extensions (covered by #2037 fix)
  • .swamp/datastore-bundles/ — datastore extensions (NOT covered)
  • .swamp/vault-bundles/ — vault extensions (NOT covered)
  • .swamp/report-bundles/ — report extensions (NOT covered)

A live managedConfig deployment hit a collision at .swamp/datastore-bundles/<hash>/s3.js during swamp datastore setup extension @swamp/s3-datastore. The category-specific bundle stores are unaffected by the current mitigation.

Reproduction

On a managedConfig serve pod with @swamp/s3-datastore already installed:

swamp datastore setup extension [@swamp](/u/swamp)/s3-datastore

Reports the #2037 error pointing at config/pulled-extensions/ with a recovery hint that lands at the wrong layout (see Lab #2048).

Expected

The warn-level conflict surfacing from #2037 should apply to all four bundle stores, not just .swamp/bundles/.

  • Lab #2037 — original collision surfacing
  • Lab #2048 — managedConfig path routing (the --force recovery hint lands at the wrong path)
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 11 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/7/2026, 9:47:54 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack729/7/2026, 8:48:10 PM

Sign in to post a ripple.