Nm Sanctum Version Updates

Bump versions, update changelogs, and coordinate version changes across files for releases

This skill appears to do exactly what it claims, but take normal precautions: (1) run the suggested --dry-run and Skill(sanctum:git-workspace-review) first, then inspect git diff and git status before committing; (2) review plugins/sanctum/scripts/update_versions.py (or any repo-local script it invokes) to ensure it only performs the expected edits; (3) run your CI/tests locally (cargo test, npm test) before publishing; (4) back up or create a branch so changes are reviewable; and (5) if you allow autonomous agent invocation, be aware the agent could apply changes to the repository when invoked — restrict that ability if you don't want automated commits without manual review.

Type: OpenClaw Skill Name: nm-sanctum-version-updates Version: 1.0.0 The skill bundle provides a workflow for automating version updates across multiple project files (Cargo.toml, package.json, pyproject.toml) and documentation. It uses standard shell commands like find, grep, and git, and references a local script (update_versions.py) to perform the updates. No evidence of data exfiltration, malicious persistence, or harmful prompt injection was found; the behavior is consistent with the stated purpose of release management.