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

Relationships

#554 @swamp/kubernetes 2026.06.04.1 missing upgrade path from 2026.05.27.2

Opened by bixu · 6/4/2026· Shipped 6/4/2026

Description

After upgrading @swamp/kubernetes from 2026.05.27.2 to 2026.06.04.1 via swamp extension pull @swamp/kubernetes --force, all existing models fail with:

Last upgrade toVersion "2026.05.27.2" does not match model version "2026.06.04.1" for model type "@swamp/kubernetes/node"

The extension's upgrades array in each model type (e.g. node.ts:225) only declares an upgrade toVersion: "2026.05.27.2". There is no entry for toVersion: "2026.06.04.1", so swamp's upgrade system rejects the version mismatch.

Steps to reproduce

  1. Have models created at @swamp/kubernetes 2026.05.27.2
  2. swamp extension pull @swamp/kubernetes --force (pulls 2026.06.04.1)
  3. Run any model method — fails with the version mismatch error

Additional issue: no CLI command to upgrade model typeVersion

There is no swamp model upgrade command. The only workaround is to manually edit the typeVersion field in each model YAML file, which doesn't work anyway because the upgrade system still rejects the mismatch. Models created at 2026.05.27.2 are effectively stuck.

Environment

  • swamp version: 20260604.165624.0-sha.9bed22cc
  • @swamp/kubernetes: upgraded from 2026.05.27.2 to 2026.06.04.1

Upstream repository: https://github.com/swamp-club/swamp-extensions

Environment

  • Extension: @swamp/kubernetes@2026.06.04.1
  • swamp: 20260604.165624.0-sha.9bed22cc
  • OS: darwin (aarch64)
  • Deno: 2.8.2
  • Shell: /bin/zsh
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 6 MOREREVIEW+ 3 MOREPR_MERGEDSHIPPED

Shipped

6/4/2026, 7:37:03 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack726/4/2026, 6:33:46 PM

Sign in to post a ripple.