Skip to content

fix: manual release and publish workflows with version updates #35

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

Merged
merged 2 commits into from
Nov 11, 2024

Conversation

Bjarten
Copy link
Owner

@Bjarten Bjarten commented Nov 10, 2024

Description

This PR updates both the release and publish workflows to:

  1. Ensure proper version updating across all package files
  2. Use manual triggers for better control and reliability

Changes

Release Workflow Updates

  • Added version: true parameter to semantic-release action
    • This ensures updates to both __init__.py and pyproject.toml versions
  • Kept explicit tag and push parameters for clarity
  • Maintained all necessary permissions

Publish Workflow Updates

  • Changed from tag-based trigger to manual workflow_dispatch
  • Simplified workflow control and verification process
  • Maintained all PyPI trusted publisher configurations

Process After Changes

  1. Manual trigger of "Create New Release" workflow:
    • Updates versions in package files
    • Creates new tag and GitHub release
  2. Manual trigger of "Publish Python Package" workflow:
    • Builds package with updated versions
    • Publishes to PyPI

@Bjarten Bjarten merged commit 45de9bb into main Nov 11, 2024
5 checks passed
@Bjarten Bjarten deleted the fix/versioning-update branch November 11, 2024 06:47
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