{"id":"0e8cfe5c-ad31-4ed7-b7cb-1c28760b400a","entityType":"agent","slug":"clawhub-athola-nm-sanctum-version-updates","name":"version-updates","canonicalUrl":"https://www.xpersona.co/agent/clawhub-athola-nm-sanctum-version-updates","canonicalPath":"/agent/clawhub-athola-nm-sanctum-version-updates","generatedAt":"2026-10-10T10:53:33.346Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T06:12:24.894Z","emptyReason":null},"description":"Bumps versions, updates changelogs, and coordinates version changes across files for releases Skill: version-updates Owner: athola Summary: Bumps versions, updates changelogs, and coordinates version changes across files for releases Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:21:27.145Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:41:26.869Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:58:14.712Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:06:02.355Z | user Release v1.9.14 v1.9.13 | 2","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.6K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-version-updates","sourceUrl":"https://clawhub.ai/athola/nm-sanctum-version-updates","homepage":"https://clawhub.ai/athola/skills/nm-sanctum-version-updates","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/athola/nm-sanctum-version-updates","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/athola/skills/nm-sanctum-version-updates","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":64,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Bumps versions, updates changelogs, and coordinates version changes across files for releases Skill: version-updates Owner: athola Summary: Bumps versions, upda"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T06:12:24.894Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T06:12:24.894Z","emptyReason":null},"stars":null,"forks":null,"downloads":1627,"packageName":null,"latestVersion":"1.9.19","tractionLabel":"1.6K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T06:12:24.838Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T06:12:24.894Z","lastCrawledAt":"2026-10-10T06:12:24.838Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T06:12:24.838Z","lastVerifiedAt":null,"highlights":[{"version":"1.9.19","createdAt":"2026-08-26T13:21:27.145Z","changelog":"Release v1.9.19","fileCount":3,"zipByteSize":3430},{"version":"1.9.17","createdAt":"2026-07-30T05:41:26.869Z","changelog":"Release v1.9.17","fileCount":3,"zipByteSize":3418},{"version":"1.9.16","createdAt":"2026-07-14T19:58:14.712Z","changelog":"Release v1.9.16","fileCount":3,"zipByteSize":3399},{"version":"1.9.14","createdAt":"2026-06-30T18:06:02.355Z","changelog":"Release v1.9.14","fileCount":3,"zipByteSize":3479},{"version":"1.9.13","createdAt":"2026-06-27T16:23:48.097Z","changelog":"Release v1.9.13","fileCount":3,"zipByteSize":3444},{"version":"1.9.12","createdAt":"2026-06-19T03:19:22.889Z","changelog":"Release v1.9.12","fileCount":3,"zipByteSize":3429},{"version":"1.0.3","createdAt":"2026-06-18T15:22:11.344Z","changelog":"Release v1.9.12","fileCount":3,"zipByteSize":3416},{"version":"1.0.2","createdAt":"2026-05-09T02:20:13.410Z","changelog":"Release v1.9.5","fileCount":3,"zipByteSize":3565}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-version-updates","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T10:53:33.344Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-version-updates/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T06:12:24.894Z","emptyReason":null},"readme":"Skill: version-updates\n\nOwner: athola\n\nSummary: Bumps versions, updates changelogs, and coordinates version changes across files for releases\n\nTags: latest:1.9.19\n\nVersion history:\n\nv1.9.19 | 2026-08-26T13:21:27.145Z | user\n\nRelease v1.9.19\n\nv1.9.17 | 2026-07-30T05:41:26.869Z | user\n\nRelease v1.9.17\n\nv1.9.16 | 2026-07-14T19:58:14.712Z | user\n\nRelease v1.9.16\n\nv1.9.14 | 2026-06-30T18:06:02.355Z | user\n\nRelease v1.9.14\n\nv1.9.13 | 2026-06-27T16:23:48.097Z | user\n\nRelease v1.9.13\n\nv1.9.12 | 2026-06-19T03:19:22.889Z | user\n\nRelease v1.9.12\n\nv1.0.3 | 2026-06-18T15:22:11.344Z | user\n\nRelease v1.9.12\n\nv1.0.2 | 2026-05-09T02:20:13.410Z | user\n\nRelease v1.9.5\n\nv1.0.1 | 2026-05-06T14:21:39.581Z | user\n\nRelease v1.9.4\n\nv1.0.0 | 2026-04-20T12:01:53.572Z | auto\n\nInitial release – provides a workflow for coordinated version bumps and changelog updates across multiple files and docs.\n\n- Automates identifying and updating all version references in config files and plugin documentation.\n- Outlines required steps: context collection, target identification, version setting, docs updating, and verification.\n- Supports both automated and manual version updates.\n- Offers detailed instructions on finding and updating nested version files and all documentation with version mentions.\n- Includes troubleshooting guidelines for common problems.\n\nArchive index:\n\nArchive v1.9.19: 3 files, 3430 bytes\n\nFiles: skill-card.md (2012b), SKILL.md (4346b), _meta.json (146b)\n\nFile v1.9.19:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n\nFile v1.9.19:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787750487145\n}\n\nFile v1.9.19:skill-card.md\n\n## Description:\n\nBumps versions, updates changelogs, and coordinates version changes across files for releases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and release maintainers use this skill to prepare releases by choosing a target version, finding version-bearing configuration and documentation files, updating changelogs and README references, and verifying the resulting diff.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The workflow can update multiple configuration and documentation files, so an incorrect target version or broad search result could create unintended release changes.\n\nMitigation: Review the dry-run output and git diff before allowing changes to proceed.\n\nRisk: Release notes and documentation updates can become inaccurate if generated from incomplete context.\n\nMitigation: Confirm the changelog entry, README references, and test results against the intended release scope before publishing.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/athola/skills/nm-sanctum-version-updates)\n- [OpenClaw Homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration]\n\n**Output Format:** [Markdown summaries with inline shell commands and file-change guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose or apply repository file edits for version metadata, changelogs, README references, and related release documentation.]\n\n## Skill Version(s):\n\n1.9.19 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.9.17: 3 files, 3418 bytes\n\nFiles: skill-card.md (2122b), SKILL.md (4346b), _meta.json (146b)\n\nFile v1.9.17:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n\nFile v1.9.17:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.9.17\",\n \"publishedAt\": 1785390086869\n}\n\nFile v1.9.17:skill-card.md\n\n## Description:
\nBumps versions, updates changelogs, and coordinates version changes across files for releases.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release engineers use this skill when preparing a release, bumping project versions, updating changelogs, and coordinating version references across project files.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Broad triggers such as version, release, changelog, semver, and bump could activate the workflow during routine discussion.
\nMitigation: Require explicit user intent before invoking the skill for release or version-bump work.
\nRisk: The workflow can guide repository-wide edits to configuration files, changelogs, README files, and documentation.
\nMitigation: Preview planned changes with dry-run or diff output before applying edits, then review git status and diffs after changes.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/athola/skills/nm-sanctum-version-updates)
\n- [ClawHub Publisher Profile](https://clawhub.ai/user/athola)
\n- [OpenClaw Homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and file-change summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May guide edits to version-bearing configuration files, changelogs, README files, and release documentation.]
\n\n## Skill Version(s):
\n1.9.17 (source: ClawHub release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.16: 3 files, 3399 bytes\n\nFiles: skill-card.md (2000b), SKILL.md (4346b), _meta.json (146b)\n\nFile v1.9.16:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n\nFile v1.9.16:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.9.16\",\n \"publishedAt\": 1784059094712\n}\n\nFile v1.9.16:skill-card.md\n\n## Description:
\nBumps versions, updates changelogs, and coordinates version changes across files for releases.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release maintainers use this skill when preparing a release or bumping a project version across configuration files, changelogs, and version references.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Broad triggers such as version, release, changelog, semver, and bump may activate the skill during ordinary release discussions.
\nMitigation: Confirm that the intended task is a release or version bump before applying the workflow.
\nRisk: Version bump workflows can affect multiple configuration and documentation files.
\nMitigation: Review the dry run, git status, and diff before allowing edits or accepting proposed changes.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-version-updates)
\n- [Sanctum plugin homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and release file-change summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include proposed version edits, changelog updates, git status, and diff excerpts.]
\n\n## Skill Version(s):
\n1.9.16 (source: server release metadata; artifact frontmatter reports 1.9.8)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.14: 3 files, 3479 bytes\n\nFiles: skill-card.md (2126b), SKILL.md (4346b), _meta.json (146b)\n\nFile v1.9.14:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n\nFile v1.9.14:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.9.14\",\n \"publishedAt\": 1782842762355\n}\n\nFile v1.9.14:skill-card.md\n\n## Description:
\nBumps versions, updates changelogs, and coordinates version changes across files for releases.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release engineers use this skill to prepare software releases by finding version-bearing files, updating changelogs and documentation, and verifying the resulting changes.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Short triggers such as \"version\" and \"release\" may activate this workflow more often than intended.
\nMitigation: Review the agent's plan before allowing file changes, especially when the task is not a release preparation task.
\nRisk: Version and changelog edits can be incomplete or incorrect across multi-package repositories.
\nMitigation: Use dry-run output where available, inspect the final diff, and run relevant tests or build checks before publishing or tagging.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-version-updates)
\n- [Project homepage from ClawHub metadata](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n- [Publisher profile](https://clawhub.ai/user/athola)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, markdown, code]
\n**Output Format:** [Markdown guidance with shell command snippets and change summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May propose or perform repository file edits for version files, changelogs, and documentation.]
\n\n## Skill Version(s):
\n1.9.14 (source: server release evidence; artifact frontmatter reports 1.9.8)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.13: 3 files, 3444 bytes\n\nFiles: skill-card.md (2108b), SKILL.md (4346b), _meta.json (146b)\n\nFile v1.9.13:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n\nFile v1.9.13:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.9.13\",\n \"publishedAt\": 1782577428097\n}\n\nFile v1.9.13:skill-card.md\n\n## Description:
\nBumps versions, updates changelogs, and coordinates version changes across files for releases.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release maintainers use this skill when preparing releases, bumping project versions, updating changelogs, and checking related documentation and configuration files.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Broad trigger words such as version, release, changelog, semver, and bump may activate the skill for adjacent maintenance requests.
\nMitigation: Phrase requests explicitly and confirm that release or version maintenance is intended before applying suggested changes.
\nRisk: Version bumps and changelog updates can affect multiple files and may introduce incorrect release metadata.
\nMitigation: Review the planned file changes and diff before allowing edits, then run the relevant tests or build checks for the changed project.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-version-updates)
\n- [Source homepage from ClawHub metadata](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, guidance]
\n**Output Format:** [Markdown guidance with command snippets and change summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May propose file edits, version updates, changelog entries, verification commands, and release follow-up steps.]
\n\n## Skill Version(s):
\n1.9.13 (source: ClawHub server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.12: 3 files, 3429 bytes\n\nFiles: skill-card.md (2093b), SKILL.md (4346b), _meta.json (146b)\n\nFile v1.9.12:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n\nFile v1.9.12:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.9.12\",\n \"publishedAt\": 1781839162889\n}\n\nFile v1.9.12:skill-card.md\n\n## Description:
\nBumps versions, updates changelogs, and coordinates version changes across files for releases.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release maintainers use this skill when preparing a release, bumping semantic versions, updating changelogs, and checking related version references across project files.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can propose edits to version and changelog files, and incorrect version updates could create misleading release metadata.
\nMitigation: Review the proposed diffs, verify the intended version number, and run the relevant project tests or builds before accepting changes.
\nRisk: Broad trigger words such as version, release, changelog, semver, and bump may activate the workflow during general discussion.
\nMitigation: Confirm that the user intends to prepare a release or update project versions before applying file changes.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-version-updates)
\n- [Sanctum plugin homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and file-change summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May propose edits to versioned configuration, changelog, README, and documentation files for user review.]
\n\n## Skill Version(s):
\n1.9.12 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.3: 3 files, 3416 bytes\n\nFiles: skill-card.md (2064b), SKILL.md (4346b), _meta.json (145b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1781796131344\n}\n\nFile v1.0.3:skill-card.md\n\n## Description:
\nBumps versions, updates changelogs, and coordinates version changes across files for releases.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release maintainers use this skill to prepare releases by finding version-bearing files, bumping versions, updating changelogs and documentation, and verifying the resulting diff.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: An incorrect target version or broad version-reference search could update release files unintentionally.
\nMitigation: Confirm the intended target version first, run the described dry run, and review git diff and changed files before committing or publishing.
\nRisk: Generated changelog or documentation updates may be incomplete or misleading.
\nMitigation: Review release notes and documentation references, then run relevant tests or builds before tagging.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/athola/nm-sanctum-version-updates)
\n- [Sanctum Plugin Homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and file-change summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May update version files and release documentation when applied by an agent; review dry-run output, git diff, and changed files.]
\n\n## Skill Version(s):
\n1.0.3 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 3 files, 3565 bytes\n\nFiles: skill-card.md (2091b), SKILL.md (4551b), _meta.json (145b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bump versions, update changelogs, and coordinate version changes across files for releases\nversion: 1.9.5\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1778293213410\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nBump versions, update changelogs, and coordinate version changes across files for releases.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and release engineers use this skill to prepare version bumps, update changelogs and documentation, and verify release-related file changes before publishing.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Version bump guidance can touch multiple project files and create incorrect release metadata if the target version is wrong.
\nMitigation: Confirm the target version before changes, prefer dry-run mode when using referenced helpers, and review the final git diff before committing, tagging, or publishing.
\nRisk: The artifact references a local helper script that is not bundled in the release artifact.
\nMitigation: Inspect any referenced local helper script in the destination repository before executing it.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-version-updates)
\n- [Clawdis homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and file-change summaries]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May propose edits across versioned configuration files, changelogs, README files, and release documentation.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release metadata; source skill frontmatter reports 1.9.5)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 2 files, 2454 bytes\n\nFiles: SKILL.md (4551b), _meta.json (145b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bump versions, update changelogs, and coordinate version changes across files for releases\nversion: 1.9.4\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1778077299581\n}\n\nArchive v1.0.0: 2 files, 2454 bytes\n\nFiles: SKILL.md (4551b), _meta.json (145b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: version-updates\ndescription: |\n Bump versions, update changelogs, and coordinate version changes across files for releases\nversion: 1.8.2\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version References\n\nThese files contain version numbers and MUST be checked during version bumps:\n\n| File | Content |\n|------|---------|\n| `docs/api-overview.md` | Plugin inventory table with all plugin versions |\n| `CHANGELOG.md` | Version history and release notes |\n| `book/src/reference/capabilities-reference.md` | May reference version-specific features |\n| Plugin READMEs | May mention plugin versions |\n\n### Scan for Additional Version References\n\n```bash\n# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations\n```\n\n### Update Sequence\n1. Update config files (pyproject.toml, plugin.json, etc.) - automated\n2. Update `CHANGELOG.md` - add new version section\n3. Update `docs/api-overview.md` - update version table and plugin details\n4. Scan for other version references and update as needed\n\n## Step 5: Verification (`verification`)\n- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).\n- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.\n\n## Output Instructions\n- Summarize the files changed and the new version number.\n- Mention follow-up steps, such as publishing or tagging, if applicable.\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1776686513572\n}","readmeExcerpt":"Skill: version-updates Owner: athola Summary: Bumps versions, updates changelogs, and coordinates version changes across files for releases Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:21:27.145Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:41:26.869Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:58:14.712Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:06:02.355Z | user Release v1.9.14 v1.9.13 | 2","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations"},{"language":"bash","snippet":"# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations"},{"language":"bash","snippet":"# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations"},{"language":"bash","snippet":"# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations"},{"language":"bash","snippet":"# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations"},{"language":"bash","snippet":"# Find all docs mentioning the OLD version\ngrep -r \"1\\.2\\.6\" docs/ book/ --include=\"*.md\" | grep -v node_modules\n\n# Common patterns to search:\n# - \"v1.2.6\", \"1.2.6\", \"(v1.2.6)\"\n# - Version tables in markdown\n# - \"Added in X.Y.Z\" annotations"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: version-updates\ndescription: |\n Bumps versions, updates changelogs, and coordinates version changes across files for releases\nversion: 1.9.8\ntriggers:\n - version\n - release\n - changelog\n - semver\n - bump\n - preparing a release or bumping the project version\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# Version Update Workflow\n\n## When To Use\nUse this skill when preparing a release or bumping the project version.\nRun `Skill(sanctum:git-workspace-review)` first to capture current changes.\n\n## When NOT To Use\n\n- Just documentation updates - use doc-updates\n- Full PR preparation - use pr-prep\n\n## Required TodoWrite Items\n1. `version-update:context-collected`\n2. `version-update:target-files`\n3. `version-update:version-set`\n4. `version-update:docs-updated`\n5. `version-update:verification`\n\n## Step 1: Collect Context (`context-collected`)\n- Confirm which version to apply (default: bump patch).\n- If the prompt provides an explicit version, note it.\n- validate `Skill(sanctum:git-workspace-review)` has already captured the repository status.\n\n## Step 2: Identify Targets (`target-files`)\n- Find ALL configuration files that store versions using recursive search:\n - Root level: `Cargo.toml`, `package.json`, `pyproject.toml`\n - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json`\n - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included\n - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v\n- Include changelog and README references that mention the version.\n- Use: `find plugins -name \"pyproject.toml\" -o -name \"Cargo.toml\" | grep -v \".venv\"`\n\n## Step 3: Update Versions (`version-set`)\n- **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py ` to update all version files\n - Supports pyproject.toml, Cargo.toml, package.json\n - Automatically excludes virtual environments\n - Finds nested version files (e.g., `plugins/memory-palace/hooks/pyproject.toml`)\n - Use `--dry-run` flag first to preview changes\n- **Manual approach**: Update each target file with the new version\n - For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format\n - If the project supports multiple packages, document each update\n\n## Step 4: Update Documentation (`docs-updated`)\n- Add or update changelog entries with today's date.\n- Refresh README and docs references to mention the new version and any release notes.\n\n### Critical Documentation Files with Version Ref"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-sanctum-version-updates\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787750487145\n}"},{"path":"skill-card.md","content":"## Description:\n\nBumps versions, updates changelogs, and coordinates version changes across files for releases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and release maintainers use this skill to prepare releases by choosing a target version, finding version-bearing configuration and documentation files, updating changelogs and README references, and verifying the resulting diff.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The workflow can update multiple configuration and documentation files, so an incorrect target version or broad search result could create unintended release changes.\n\nMitigation: Review the dry-run output and git diff before allowing changes to proceed.\n\nRisk: Release notes and documentation updates can become inaccurate if generated from incomplete context.\n\nMitigation: Confirm the changelog entry, README references, and test results against the intended release scope before publishing.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/athola/skills/nm-sanctum-version-updates)\n- [OpenClaw Homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration]\n\n**Output Format:** [Markdown summaries with inline shell commands and file-change guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose or apply repository file edits for version metadata, changelogs, README references, and related release documentation.]\n\n## Skill Version(s):\n\n1.9.19 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Bumps versions, updates changelogs, and coordinates version changes across files for releases Skill: version-updates Owner: athola Summary: Bumps versions, updates changelogs, and coordinates version changes across files for releases Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:21:27.145Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:41:26.869Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:58:14.712Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:06:02.355Z | user Release v1.9.14 v1.9.13 | 2","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1046,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T06:12:24.894Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T06:12:24.894Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T10:53:33.346Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}