fix: bump to 1.5.0 and use trusted publisher for PyPI#130
Merged
Conversation
…eploy - Update pyproject.toml version from 1.4.2 to 1.5.0 - Replace username/password auth with PyPI OIDC trusted publisher - Fix poetry.lock inconsistency Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pypa/gh-action-pypi-publish)Context
Previous deploy failed with
403: User 'apitable' does not have a verified primary email address. Trusted Publishers bypass this by using GitHub OIDC tokens instead.Before publishing
Need to configure Trusted Publisher on PyPI:
apitable/apitable-sdks, workflowpy-deploy.ymlTest plan
apitable.py@1.5.0on develop to trigger publish🤖 Generated with Claude Code