القائمة
Step-by-step release workflow for publishing ftree-kg to PyPI using Poetry. Use this skill when the user wants to cut a release, bump the version, update the CHANGELOG, tag a commit, build and publish to PyPI, or run any part of the release pipeline for the ftree-kg project.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | publish |
| description | Step-by-step release workflow for publishing ftree-kg to PyPI using Poetry. Use this skill when the user wants to cut a release, bump the version, update the CHANGELOG, tag a commit, build and publish to PyPI, or run any part of the release pipeline for the ftree-kg project. |
git status shows no uncommitted changes)poetry run pytest)pre-commit run --all-files)poetry config pypi-token.pypi <token>)Follow Semantic Versioning:
| Change | Bump |
|---|---|
| Bug fixes only | patch (0.5.2 → 0.5.3) |
| New features, backward-compatible | minor (0.5.2 → 0.6.0) |
| Breaking changes | major (0.5.2 → 1.0.0) |
Move items from ## [Unreleased] to a new versioned section:
## [X.Y.Z] - YYYY-MM-DD
Leave ## [Unreleased] empty at the top for future entries.
poetry version patch # or minor / major
Verify: grep '^version' pyproject.toml
git add pyproject.toml CHANGELOG.md
FTREEKG_SKIP_SNAPSHOT=1 git commit -m "chore: release vX.Y.Z"
Use
FTREEKG_SKIP_SNAPSHOT=1to prevent the post-commit hook from creating a snapshot on a release commit.
git tag -a vX.Y.Z -m "Release vX.Y.Z"
poetry build
Artifacts appear in dist/. Verify they look correct:
ls -lh dist/
poetry publish
To test against TestPyPI first:
poetry publish -r testpypi
git push origin main --tags
ftreekg snapshot save X.Y.Z --repo . --commit $(git rev-parse HEAD) --branch mainIf something went wrong after poetry publish:
poetry run twine yank ftree-kg X.Y.Zgit revert HEAD then git pushgit tag -d vX.Y.Z && git push origin :refs/tags/vX.Y.Z