Skip to content

ci(python-sdk): auto-increment from agentmail-python, not the Vapi template repo - #254

Open
sidharth0612 wants to merge 1 commit into
mainfrom
claude/fix-python-release-version
Open

sidharth0612 wants to merge 1 commit into
mainfrom
claude/fix-python-release-version

Conversation

@sidharth0612

Copy link
Copy Markdown
Contributor

Summary

The Release Python SDK workflow's auto-increment (used when version is left blank) fetched the latest release from VapiAI/server-sdk-python, a leftover from the template it was copied from. That repo is at 2.0.0, so a dispatch without an explicit version on 2026-09-18 computed and published agentmail 2.0.1 to PyPI instead of 0.6.1.

This PR points the lookup at agentmail-to/agentmail-python (releases first, tags as fallback), so the next blank-version dispatch increments from our own latest release.

The TypeScript workflow requires an explicit version and has no such lookup.

Test plan

  • Only the three repo references change; the version-parsing logic is untouched
  • Next Python release dispatched without version increments from the current agentmail-python latest release

🤖 Generated with Claude Code

…mplate repo

The Release Python SDK workflow's auto-increment fetched the latest release
from VapiAI/server-sdk-python, left over from the template it was copied from.
That repo is at 2.0.0, so a dispatch without an explicit version on 2026-09-18
published agentmail 2.0.1 to PyPI instead of 0.6.1. Read our own SDK repo's
latest release and tags instead.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

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