Dstack Upgrade

/upgrade

Upgrade data-stack to the latest version and show what's new.

Inline upgrade flow

This section is referenced by all skill preambles when they detect UPGRADE_AVAILABLE.

Step 1: Ask the user (or auto-upgrade)

First, check if auto-upgrade is enabled:

_AUTO=""
[ "${DATA_STACK_AUTO_UPGRADE:-}" = "1" ] && _AUTO="true"
[ -z "$_AUTO" ] && _AUTO=$(~/.claude/skills/data-stack/bin/data-stack-config get auto_upgrade 2>/dev/null || .claude/skills/data-stack/bin/data-stack-config get auto_upgrade 2>/dev/null || true)
echo "AUTO_UPGRADE=$_AUTO"

If AUTO_UPGRADE=true or AUTO_UPGRADE=1: Skip AskUserQuestion. Log "Auto-upgrading data-stack v{old} → v{new}..." and proceed directly to Step 2. If ./install.sh fails during auto-upgrade, restore from backup (.bak directory) and warn the user: "Auto-upgrade failed — restored previous version. Run /upgrade manually to retry."

Otherwise, use AskUserQuestion:

• Question: "data-stack v{new} is available (you're on v{old}). Upgrade now?"
• Options: ["Yes, upgrade now", "Always keep me up to date", "Not now", "Never ask again"]

If "Yes, upgrade now": Proceed to Step 2.

If "Always keep me up to date":

~/.claude/skills/data-stack/bin/data-stack-config set auto_upgrade true 2>/dev/null || .claude/skills/data-stack/bin/data-stack-config set auto_upgrade true 2>/dev/null

Tell user: "Auto-upgrade enabled. Future updates will install automatically." Then proceed to Step 2.

If "Not now": Write snooze state with escalating backoff (first snooze = 24h, second = 48h, third+ = 1 week), then continue with the current skill. Do not mention the upgrade again.

_SNOOZE_FILE="${DATA_STACK_STATE_DIR:-$HOME/.data-stack}/update-snoozed"
_REMOTE_VER="{new}"
_CUR_LEVEL=0
if [ -f "$_SNOOZE_FILE" ]; then
  _SNOOZED_VER=$(awk '{print $1}' "$_SNOOZE_FILE")
  if [ "$_SNOOZED_VER" = "$_REMOTE_VER" ]; then
    _CUR_LEVEL=$(awk '{print $2}' "$_SNOOZE_FILE")
    case "$_CUR_LEVEL" in *[!0-9]*) _CUR_LEVEL=0 ;; esac
  fi
fi
_NEW_LEVEL=$((_CUR_LEVEL + 1))
[ "$_NEW_LEVEL" -gt 3 ] && _NEW_LEVEL=3
echo "$_REMOTE_VER $_NEW_LEVEL $(date +%s)" > "$_SNOOZE_FILE"

Note: {new} is the remote version from the UPGRADE_AVAILABLE output — substitute it from the update check result.

Tell user the snooze duration: "Next reminder in 24h" (or 48h or 1 week, depending on level). Tip: "Set auto_upgrade: true in ~/.data-stack/config.yaml for automatic upgrades."

If "Never ask again":

~/.claude/skills/data-stack/bin/data-stack-config set update_check false 2>/dev/null || .claude/skills/data-stack/bin/data-stack-config set update_check false 2>/dev/null

Tell user: "Update checks disabled. Run ~/.claude/skills/data-stack/bin/data-stack-config set update_check true to re-enable." Continue with the current skill.

Step 2: Detect install type

if [ -d "$HOME/.claude/skills/data-stack/.git" ]; then
  INSTALL_TYPE="global-git"
  INSTALL_DIR="$HOME/.claude/skills/data-stack"
elif [ -d ".claude/skills/data-stack/.git" ]; then
  INSTALL_TYPE="local-git"
  INSTALL_DIR=".claude/skills/data-stack"
elif [ -d ".claude/skills/data-stack" ]; then
  INSTALL_TYPE="vendored"
  INSTALL_DIR=".claude/skills/data-stack"
elif [ -d "$HOME/.claude/skills/data-stack" ]; then
  INSTALL_TYPE="vendored-global"
  INSTALL_DIR="$HOME/.claude/skills/data-stack"
else
  echo "ERROR: data-stack not found"
  exit 1
fi
echo "Install type: $INSTALL_TYPE at $INSTALL_DIR"

Step 3: Save old version

OLD_VERSION=$(cat "$INSTALL_DIR/VERSION" 2>/dev/null || echo "unknown")

Step 4: Upgrade

For git installs (global-git, local-git):

cd "$INSTALL_DIR"
STASH_OUTPUT=$(git stash 2>&1)
git fetch origin
git reset --hard origin/main
./install.sh

If $STASH_OUTPUT contains "Saved working directory", warn the user: "Note: local changes were stashed. Run git stash pop in the skill directory to restore them."

For vendored installs (vendored, vendored-global):

PARENT=$(dirname "$INSTALL_DIR")
TMP_DIR=$(mktemp -d)
git clone --depth 1 https://github.com/Upsolve-Labs/data-stack.git "$TMP_DIR/data-stack"
mv "$INSTALL_DIR" "$INSTALL_DIR.bak"
mv "$TMP_DIR/data-stack" "$INSTALL_DIR"
cd "$INSTALL_DIR" && ./install.sh
rm -rf "$INSTALL_DIR.bak" "$TMP_DIR"

Step 4.5: Sync local vendored copy

After upgrading the primary install, check if there's also a local copy in the current project that needs updating:

_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
LOCAL_UPSTACK=""
if [ -n "$_ROOT" ] && [ -d "$_ROOT/.claude/skills/data-stack" ]; then
  _RESOLVED_LOCAL=$(cd "$_ROOT/.claude/skills/data-stack" && pwd -P)
  _RESOLVED_PRIMARY=$(cd "$INSTALL_DIR" && pwd -P)
  if [ "$_RESOLVED_LOCAL" != "$_RESOLVED_PRIMARY" ]; then
    LOCAL_UPSTACK="$_ROOT/.claude/skills/data-stack"
  fi
fi
echo "LOCAL_UPSTACK=$LOCAL_UPSTACK"

If LOCAL_UPSTACK is non-empty, update it by copying from the freshly-upgraded primary install:

mv "$LOCAL_UPSTACK" "$LOCAL_UPSTACK.bak"
cp -Rf "$INSTALL_DIR" "$LOCAL_UPSTACK"
rm -rf "$LOCAL_UPSTACK/.git"
cd "$LOCAL_UPSTACK" && ./install.sh
rm -rf "$LOCAL_UPSTACK.bak"

Tell user: "Also updated vendored copy at $LOCAL_UPSTACK — commit .claude/skills/data-stack/ when you're ready."

Step 5: Write marker + clear cache

mkdir -p "${DATA_STACK_STATE_DIR:-$HOME/.data-stack}"
echo "$OLD_VERSION" > "${DATA_STACK_STATE_DIR:-$HOME/.data-stack}/just-upgraded-from"
rm -f "${DATA_STACK_STATE_DIR:-$HOME/.data-stack}/last-update-check"
rm -f "${DATA_STACK_STATE_DIR:-$HOME/.data-stack}/update-snoozed"

Step 6: Show What's New

Read $INSTALL_DIR/CHANGELOG.md. Find all version entries between the old version and the new version. Summarize as 5-7 bullets grouped by theme. Focus on user-facing changes.

Format:

data-stack v{new} — upgraded from v{old}!

What's new:
- [bullet 1]
- [bullet 2]
- ...

Happy shipping!

Step 7: Continue

After showing What's New, continue with whatever skill the user originally invoked. The upgrade is done — no further action needed.

Standalone usage

When invoked directly as /upgrade (not from a preamble), follow Steps 2-6 above. If already on the latest version, tell the user: "You're already on the latest version (v{version})."