How to release a new pgdbm library version to PyPI
This skill guides you through releasing a new version of the pgdbm library.
uv run pytest
All tests must pass before releasing.
Three files need version updates:
# Check current version
grep "^version" pyproject.toml
Update these files to the new version:
| File | Location |
|---|---|
pyproject.toml | version = "X.Y.Z" |
src/pgdbm/__version__.py | __version__ = "X.Y.Z" |
.claude-plugin/plugin.json | "version": "X.Y.Z" |
Important: The plugin.json version controls Claude Code skill caching. Always bump it when releasing.
Add entry at the top:
## [X.Y.Z] - YYYY-MM-DD
### Added
- New features
### Changed
- Changes to existing features
### Fixed
- Bug fixes
git add pyproject.toml src/pgdbm/__version__.py .claude-plugin/plugin.json CHANGELOG.md uv.lock
git commit -m "chore: bump version to X.Y.Z
- Summary of changes
Co-Authored-By: Claude Opus 4.5 <[email protected]>"
git tag -a vX.Y.Z -m "Release X.Y.Z"
git push origin main
git push origin vX.Y.Z
Important: Clean the dist/ directory first to avoid uploading old versions.
rm -rf dist/
uv build
uv publish
Or if using twine:
rm -rf dist/
uv build
twine upload dist/*
# Check PyPI
pip index versions pgdbm
# Check plugin update works
claude plugin update pgdbm@juanre-ai-tools
Follow semver:
publish-skills skill