version-updates
/version-updates
Podbija wersje, aktualizuje changelogi i koordynuje zmiany wersji w plikach przy przygotowaniu wydania.
- Autor
- athola ↗
- Repozytorium
- claude-night-market ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 01.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 01.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Podbija wersje, aktualizuje changelogi i koordynuje zmiany wersji w plikach przy przygotowaniu wydania.
Oryginalny opis (EN)
Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.
Jak działa
- When To Use
- When NOT To Use
- Required TodoWrite Items
- Step 1: Collect Context (context-collected)
- Step 2: Identify Targets (target-files)
- Step 3: Update Versions (version-set)
- Step 4: Update Documentation (docs-updated)
- Step 5: Verification (verification)
- Output Instructions
- Exit Criteria
Podgląd SKILL.md
---
name: version-updates
description: Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.
alwaysApply: false
category: artifact-generation
tags:
- version
- release
- changelog
- semver
- bump
tools: []
complexity: medium
model_hint: standard
estimated_tokens: 700
dependencies:
- sanctum:git-workspace-review
---
# 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
1. `version-update:context-collected`
2. `version-update:target-files`
3. `version-update:version-set`
4. `version-update:docs-updated`
5. `version-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/pyproject.toml` must be included
- Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v
- 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/pyproject.toml`)
- Use `--dry-run` flag first to preview changes
- **Manual approach**: Update each target file with the new version
- For semantic versions, follow `MAJOR.MINOR.PATCH` or the specified format
- If the project supports multiple packages, document each update
## 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
```bash
# Find all docs mentioning the OLD version
grep -r "1\.2\.6" docs/ book/ --include="*.md" | grep -v node_modules
# Common patterns to search:
# - "v1.2.6", "1.2.6", "(v1.2.6)"
# - Version tables in markdown
# - "Added in X.Y.Z" annotations
```
### Update Sequence
1. Update config files (pyproject.toml, plugin.json, etc.) - automated
2. Update `CHANGELOG.md` - add new version section
3. Update `docs/api-overview.md` - update version table and plugin details
4. Scan for other version references and update as needed
## Step 5: Verification (`verification`)
- Run relevant builds or tests if version bumps require them (e.g., `cargo test`, `npm test`).
- Show `git status -sb` and `git diff` excerpts to confirm the version bumps.
## Output Instructions
- Summarize the files changed and the new version number.
- Mention follow-up steps, such as publishing or tagging, if applicable.
## Exit Criteria
- [ ] All 5 TodoWrite items (`version-update:context-collected`
through `version-update:verification`) are created before any
file is modified and marked complete in order
- [ ] `update_versions.py --dry-run <version>` run first and its
output reviewed before any version file is written
- [ ] Version bumped consistently across all found config files
(`pyproject.toml`, `Cargo.toml`, `package.json`, `plugin.json`)
with no target file missing the update
- [ ] `CHANGELOG.md` updated with a new version section dated today
- [ ] `git diff` output confirms version changes in all identified
target files; a summary of files changed and new version number
is reported to the user
Wersje
W bazie nie ma innych skilli o nazwie version-updates.
Migawka bazy z 13.11.2026 · wersja paczki 027c4fc222c8 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95release-manager
Tworzy nowe wydania AILANG: podbija wersje, aktualizuje changelog, dodaje tagi gita i sprawdza CI/CD. - 100version
Podbija wersje i tworzy wydania: aktualizuje plugin.json i marketplace.json oraz tworzy tag git i commit. - 100release
Planuje zakres wersji, weryfikuje integralność wydania (commit i CHANGELOG, tag i artefakty), generuje changelogi i przeprowadza pełne wydania. - 100create-release
Automatyzuje wydania w stylu semver w różnych typach projektów: wykrywa pliki wersji, podnosi wersję, aktualizuje changelog, tworzy tagi git i opcjonalnie publikuje wydania GitHub. - 100fluid-release
Prowadzi wydania grupy Fluid Framework: wydania minor i patch, gałęzie, podbicia wersji, changelogi i aktualizację testów typów. - 100update-plugin-release
Przygotowuje wydanie wtyczki Postgres Skills: wybiera wersję semantyczną, aktualizuje manifesty i dwa changelogi.