OpenClaw Upgrade Standard

Safe OpenClaw upgrade procedure with backup, doctor fix, service migration, rollback, and post-upgrade testing. Prevents silent failures from Dashboard upgra...

This procedure appears legitimate and coherent, but take these precautions before following it: - Inspect and, if needed, adjust the BACKUP_DIR path. Backups include credentials and should be stored securely (restrict filesystem permissions and consider encrypting the backup archive). - Confirm your npm global prefix matches the script's assumed path (~/.npm-global); adapt the entrypoint checks if your npm global modules are located elsewhere. - Run the commands as the same user who runs the OpenClaw user service (systemctl --user) to avoid permission mismatches. - Review the sed replacement step before running it (make a copy of the service file first) to avoid corrupting the unit file. - Test the procedure in a staging environment if possible before applying in production. If you want extra assurance, provide the exact environment (OS, npm prefix) or a copy of your openclaw-gateway.service and I can point out any adjustments needed.

Type: OpenClaw Skill Name: openclaw-upgrade-standard Version: 1.0.0 The skill bundle provides a structured and safe procedure for upgrading the OpenClaw software, including backup, version verification, and systemd service maintenance. All commands (npm, systemctl, sed, cp) are directly aligned with the stated administrative purpose, and sensitive data like credentials are only handled locally within a backup directory (SKILL.md).