360 Secure SkillHub
360 安全技能中心

OpenClaw Updater

通过 bash 脚本为 OpenClaw 提供更新前后的安全流程:预检时提交各 workspace 的 git 改动、备份 openclaw.json 并记录当前版本;更新后经 Telegram 通知并检查状态;失败时用 npm 安装旧版本并恢复配置回滚。

bigsan
bigsan
热度 79.30
最近更新 2026-05-17 12:36:12
分类:自动化依赖:代码执行 / 读写文件 / 第三方 API应用场景:DevOps / 自动化脚本 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add openclaw-updater
Metadata
name
openclaw-updater
description
Safely update OpenClaw with pre-flight checks and rollback support. Use when updating OpenClaw, checking for updates, or recovering from a failed update. Handles workspace git commits, config backups, version rollback, and post-update verification.

OpenClaw Updater

Safely update OpenClaw with automatic pre-flight safety checks and rollback capability.

Pre-Update Checklist

Before running openclaw update, always run the pre-update script:

bash scripts/pre-update.sh

Optional: specify a backup script to run during pre-flight:

BACKUP_SCRIPT=~/repo/scripts/backup-openclaw.sh bash scripts/pre-update.sh

The script will:

  1. Find all workspace* directories under ~/.openclaw/
  2. Git commit any uncommitted changes (init git if missing)
  3. Back up openclaw.json to /tmp/openclaw.json.bak
  4. Run the backup script if provided
  5. Save the current version to /tmp/openclaw-prev-version.txt

Telegram Notification Setup

The update script sends success/failure notifications via Telegram Bot API (bypasses OpenClaw gateway, so it works even if the update breaks the gateway).

Create ~/.openclaw/.telegram-notify.env:

TELEGRAM_BOT_TOKEN=<your-bot-token>
TELEGRAM_CHAT_ID=<your-chat-id>
chmod 600 ~/.openclaw/.telegram-notify.env

The bot token is the same one used by your OpenClaw Telegram channel. Chat ID can be found via openclaw directory.

Update (with notification)

Run the full update with automatic pre-flight + notification:

bash scripts/update.sh

This will: pre-flight → update → wait for gateway → notify via Telegram.

Update (manual)

After pre-flight passes:

openclaw update

Post-Update Verification

After updating, verify:

openclaw status
openclaw gateway status

Check that:

  • Version shows the new release
  • Gateway is running
  • All agents are responsive

Rollback

If the update breaks something:

bash scripts/rollback.sh

The script will:

  1. Read the saved previous version from /tmp/openclaw-prev-version.txt
  2. Install that version via npm install -g openclaw@<version>
  3. Optionally restore openclaw.json from backup
  4. Restart the gateway

Manual Rollback

If the rollback script isn't available:

# Install specific version
npm install -g openclaw@<version>

# Restore config
cp /tmp/openclaw.json.bak ~/.openclaw/openclaw.json

# Restart
openclaw gateway restart

Restore from Full Backup

If config and workspaces are both corrupted:

# Find latest backup
ls -t ~/repo/backups/openclaw-*.tar.gz | head -1

# Restore (overwrites ~/.openclaw/)
tar xzf ~/repo/backups/openclaw-<timestamp>.tar.gz -C ~/