#146

feat: add support for Nix via a flake

s12d ago

← Back to list

01Issue

BugShippedSwamp CLITeam

Assigneesstack72

Relationships

#920 repo upgrade reports success but extension commands still warn about pending migration

Opened by evrardjp · 7/2/2026· Shipped 7/2/2026

Description

swamp extension rm warns that extensions are pending migration and tells the user to run swamp repo upgrade. Running swamp repo upgrade reports success, but the next extension command still shows the same pending-migration warning.

This makes it look like the upgrade command completed without actually clearing the migration state, or that the warning does not reflect what repo upgrade is able to fix.

Steps to reproduce

In a repository where extension commands warn about pending migration, run:
```
swamp extension rm @magistr/fc-agent-proxy
```

Observe the warning:

warning extension·rm         5 extension(s) pending migration. Run 'swamp repo upgrade' to complete.

Complete or cancel the extension removal prompt.
Run:
```
swamp repo upgrade
```

Observe output like:

info    extension·install    Reading lockfile...
info    extension·install    All extensions up to date.
info    repo·upgrade         Upgraded swamp repository: "20260630.112427.0" → "20260630.112427.0" (tools: "pi")
info    repo·upgrade           Changed files:
info    repo·upgrade             .swamp.yaml

Run another extension command, for example:

swamp extension rm @magistr/fc-task-server@2026.06.12.1

Expected behavior

After swamp repo upgrade reports success, extension commands should no longer warn that extensions are pending migration. If migration cannot be completed, repo upgrade should report an actionable reason and identify what remains pending.

Actual behavior

The same warning is shown again:

warning extension·rm         5 extension(s) pending migration. Run 'swamp repo upgrade' to complete.

Environment

Current swamp version: 20260630.112427.0-sha.0e5078e9
swamp update --check --json reports latest available: 20260702.205250.0-sha.1ba549d7
The issue was observed on the current installed version above; I did not verify whether the latest available version changes this behavior.

Fix scope

This affects repository upgrade / extension migration state handling. The fix would likely involve making repo upgrade reconcile the pending-extension migration marker/state that extension commands check, or making the extension-command warning point to the correct recovery action when repo upgrade cannot clear it.

02Bog Flow

Shipped

7/2/2026, 10:02:40 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack727/2/2026, 9:17:11 PM

stack72 commented 7/2/2026, 10:02:51 PM

Thanks @evrardjp for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Scorecard: beta/rc-only extensions show "not scored" despite successful scoring (GET /score resolves only latestVersion)

`swamp extension search --channel beta|rc|stable` ignores the filter — all channels + the no-flag default return an identical result set

Beta-channel extensions are never scored — perpetual 'Scoring is taking longer than expected'

feat: allow models to call other models mid-execution via context.runModel()

swamp-club: enable OAuth provider for swamp serve collective-based admission

extension update/install reports new version while on-disk pulled files stay old

command/shell: step with timeout + a surviving child process reports exit -1 despite command exiting 0

swamp serve startup/shutdown is very slow on large repo and lacks diagnostics

Vault push log overstates what left the machine: Pushed N vault file(s) to datastore counts every dirty file, not just vault files

serve-auth: mode: oauth — device grant client + collective-based admission

serve-auth: enable OIDC Provider + Device Authorization plugins in swamp-club

Orphaned data (migrated-away/deleted model) can't be GC'd or deleted

Docs: document swamp data prune (orphaned-data reclamation)

UAT: CLI coverage for swamp data prune (orphaned-data reclamation)

Session credential revocation scans entire credential map on every dispatch completion

Docs: update worker-commands.md for --all flag and JSON output change

datastore migrate-index aborts on hardcoded 30s S3 requestTimeout for large shards

swamp worker list: hide disconnected workers by default, add --all flag

swamp serve should survive bad extension failures

Worker fleets phase 7: how-to guides and explanation docs

swamp serve: catch unhandled promise rejections from extensions

[@adam/cfgmgmt] SSH helper can crash swamp serve via unhandled finally() rejection

Docs: add --server-token flag to worker connect reference

Add --server-token to worker connect for authenticated orchestrators

Docs: document --trusted-hosts flag for swamp serve

Document SWAMP_SERVE_EXTRA_HEADERS for reverse proxy/tunnel setups

Add --trusted-hosts flag to swamp serve for Docker/Kubernetes worker connections

Allow swamp clients to send custom headers when connecting to swamp serve

Docs: update serve-flags.md default queue timeout from 60s to 10m

Worker fleets phase 6: raise default queue timeout to 10 minutes

Worker fleets phase 4b: capacity slots and concurrent dispatch

MethodContext docs/comments mention context.putSecret but runtime exposes vaultService.put

Docs: add --concurrency flag and SLOTS column to worker-commands reference

install.sh still points users to systeminit/swamp

Support user systemd units for 'swamp serve daemon enable'

swamp serve scheduled execution runs steps in an isolated data scope: readResource sees empty state, writeResource never reaches the model-scope chain — stateful scheduled workflows duplicate instead of deduplicating

Support installing swamp via mise GitHub backend

Worker fleets phase 4a: dispatch runner extraction — child process per dispatch

Docs: add swamp worker daemon enable/disable/status to worker-commands reference

Worker fleets phase 3 PR2: swamp worker daemon enable

Docs: add drain, lifecycle policies, and exit-code contract to references

Worker fleets phase 3 PR1: drain state machine, lifecycle policies, signal handling

Leaderboard search excludes ghosts — a visible ghost can't be found by its alias

issue-lifecycle: plan lifecycle entry silently dropped when summary exceeds 1000 chars

Docs: add worker verify, --verify-on-enroll, and env-var config to references

Labs - Filters do not apply to Blocked status and Billing Tier category

Worker fleets phase 2 PR2: env-var config, swamp worker verify, --verify-on-enroll

Docs: add --type flag to issue edit reference and how-to

Docs: update manual with whole-field expression syntax for workflow task inputs/globalArgs

Allow changing an existing issue to security/confidential after submission

Allow dynamic object expressions for workflow task inputs/globalArgs

Docs: update enrollment token references for fleet tokens (--max-enrollments)

Worker fleets phase 2 PR1: fleet tokens (--max-enrollments, bindings, worker naming)

$identify events are never consumed — anonymous web history never binds to the account

Worker fleets phase 1 PR3: boot reconciliation and integration test

Login success still shows login tip

Support confidential visibility for non-security issues

Fine-grained scopes for swamp.club access tokens

Add associative info to user profiles: collective membership + collaborative contributions

Remove comments from /feed and redesign the page

feed_post_score_events queue grows unboundedly (no TTL, no delete-on-delivery)

Make paid subscribers visually stand out (badge, profile popup summary)

Relax the profanity filter

Giphy integration via /giphy command

@-mention autocomplete for users when writing lab ripples

Worker fleets phase 1 PR2: step_queued events, pending-dispatch model, queue introspection

Docs: add swamp worker queue to worker-commands reference

/lab shipped list is sorted by issue number, not ship date

Docs: update manual for ephemeral data and step-output dependency deferral

Docs: update remote execution references for elastic queueing

Support dynamic host discovery from external sources

Worker fleets phase 1: elastic queueing

catalog backfill should support scoped population for targeted lookups

Docs: document global skill sync behavior for custom tools in manual

swamp update syncs global skills to default agent directories instead of configured custom Pi skillsDir

coerceToSuffix does not sanitize path-unsafe characters, causing forEach items and vary dimensions with / to produce invalid data instance names

Badge for activity on other people's issues

swamp serve: add @keychain=<service>/<account> indirection for secret args on macOS

swamp serve: eliminate wrapper scripts via @vault= secret refs and native startup hooks

Automate mechanical frontmatter fixes in the fixing stage