Publish the backend (deepsel-cms) package to PyPI by bumping version, committing, tagging, and pushing
Publish deepsel-cms to PyPI via the GitHub Actions tag-push workflow.
$0 — (Optional) Bump level: patch (default), minor, or major.If no argument is provided, default to patch.
Run all checks from the backend/ directory:
cd backend && make prepush
If any check fails, fix the errors and re-run. Do NOT proceed until all checks pass.
cd backend && make check-dist
This builds the distribution and validates it with twine. Fix any errors before proceeding.
backend-v* tag:
git log --oneline $(git describe --tags --match 'backend-v*' --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD -- backend/
patch if uncertain.cd backend && make bump-{level}
Read the new version:
grep '^version = ' backend/pyproject.toml
pip index versions deepsel-cms 2>/dev/null | head -5
If the new version is already on PyPI, bump again or ask the user.
Ask: "Publishing deepsel-cms v{version} — continue?"
git add backend/pyproject.toml
git commit -m "bump backend v{version}"
git tag -a backend-v{version} -m "deepsel-cms v{version}"
git push origin backend-v{version}
Do NOT push main — only push the tag.
git ls-remote --tags origin | grep backend-v{version}backend-v{version} pushed — GitHub Actions will publish to PyPI.git push origin mainhttps://github.com/DeepselSystems/deepsel-cms/actions--no-verify when committing.