version-updates
Bump versions, update changelogs, and coordinate version changes across files for releases
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/athola/nm-sanctum-version-updatesNight Market Skill — ported from claude-night-market/sanctum. For the full experience with agents, hooks, and commands, install the Claude Code plugin.
Version Update Workflow
When To Use
Use this skill when preparing a release or bumping the project version.
Run Skill(sanctum:git-workspace-review) first to capture current changes.
When NOT To Use
- Just documentation updates - use doc-updates
- Full PR preparation - use pr-prep
Required TodoWrite Items
version-update:context-collectedversion-update:target-filesversion-update:version-setversion-update:docs-updatedversion-update:verification
Step 1: Collect Context (context-collected)
- Confirm which version to apply (default: bump patch).
- If the prompt provides an explicit version, note it.
- validate
Skill(sanctum:git-workspace-review)has already captured the repository status.
Step 2: Identify Targets (target-files)
- Find ALL configuration files that store versions using recursive search:
- Root level:
Cargo.toml,package.json,pyproject.toml - Nested directories: Use glob to find
*/pyproject.toml,*/Cargo.toml,*/package.json - Example:
plugins/memory-palace/hooks/pyproject.tomlmust be included - Exclude virtual environments (
.venv,node_modules,target/) using grep -v
- Root level:
- Include changelog and README references that mention the version.
- Use:
find plugins -name "pyproject.toml" -o -name "Cargo.toml" | grep -v ".venv"
Step 3: Update Versions (version-set)
- Automated approach: Use
plugins/sanctum/scripts/update_versions.py <version>to update all version files- Supports pyproject.toml, Cargo.toml, package.json
- Automatically excludes virtual environments
- Finds nested version files (e.g.,
plugins/memory-palace/hooks/pyproject.toml) - Use
--dry-runflag first to preview changes
- Manual approach: Update each target file with the new version
- For semantic versions, follow
MAJOR.MINOR.PATCHor the specified format - If the project supports multiple packages, document each update
- For semantic versions, follow
Step 4: Update Documentation (docs-updated)
- Add or update changelog entries with today's date.
- Refresh README and docs references to mention the new version and any release notes.
Critical Documentation Files with Version References
These files contain version numbers and MUST be checked during version bumps:
| File | Content |
|---|---|
docs/api-overview.md | Plugin inventory table with all plugin versions |
CHANGELOG.md | Version history and release notes |
book/src/reference/capabilities-reference.md | May reference version-specific features |
| Plugin READMEs | May mention plugin versions |
Scan for Additional Version References
# Find all docs mentioning the OLD version
grep -r "1\.2\.6" docs/ book/ --include="*.md" | grep -v node_modules
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-athola-nm-sanctum-version-updates": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
extract
Analyze a codebase and build a knowledge base of business logic, architecture, data flow, and engineering patterns. The foundation for gauntlet challenges and agent integration
discourse
>- Scan community discussion channels (HN, Lobsters, Reddit, tech blogs) for experience reports and opinions on a topic
synthesize
>- Merge, deduplicate, rank, and format research findings from multiple channels into a coherent report. Use after research agents return their results
workflow-monitor
Detect workflow failures and inefficient patterns, then create GitHub issues for improvement via /fix-workflow
architecture-paradigm-hexagonal
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure