Skip to content

fix(ci): auto-set PyPI version from tag#131

Merged
zoe-icu merged 2 commits into
apitable:developfrom
zoe-icu:fix/py-deploy-auto-version
Jul 9, 2026
Merged

fix(ci): auto-set PyPI version from tag#131
zoe-icu merged 2 commits into
apitable:developfrom
zoe-icu:fix/py-deploy-auto-version

Conversation

@zoe-icu

@zoe-icu zoe-icu commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Extract version from git tag name (e.g. apitable.py@1.5.01.5.0) via poetry version at build time
  • No longer requires manual pyproject.toml version bumps before release
  • Uses API token auth (PYPI_USERNAME/PYPI_PASSWORD secrets) instead of trusted publisher
  • Removes stale paths trigger that doesn't apply to tag-based workflows

Context

Previous publish failed because pyproject.toml was still at 1.4.2 while the tag was 1.5.0. This fix makes the version always match the tag automatically.

Test plan

  • Push tag apitable.py@1.5.0 after merge to trigger publish
  • Verify PyPI receives version 1.5.0

🤖 Generated with Claude Code

zoe-icu and others added 2 commits July 9, 2026 14:33
Extract version from tag name (e.g. apitable.py@1.5.0 → 1.5.0) so
pyproject.toml no longer needs manual version bumps before release.
Reverts to username/password auth since we don't have PyPI trusted
publisher access.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Keep API token auth with auto-version from tag, discard trusted publisher changes.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@zoe-icu zoe-icu merged commit 225fdd1 into apitable:develop Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant