-
Notifications
You must be signed in to change notification settings - Fork 6
Workflow for publishing to PyPI #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow for publishing to PyPI #57
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a new GitHub Actions workflow for publishing the seclab-taskflow-agent package to PyPI. The workflow is triggered on version tags and handles building, signing, publishing, and creating GitHub releases.
- Adds automated PyPI publishing workflow triggered by version tags
- Implements package signing with sigstore
- Creates GitHub releases with distribution artifacts
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
fbe9f67 to
76b46e9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
b1d0a48 to
c39bd5e
Compare
|
I am not a code owner! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
c09d9d4 to
b371318
Compare
This workflow is almost identical to
publish-to-testpypi.yaml. The main difference is that it's triggered by pushing a tag with a name likev0.0.1.