Skip to content

build(release): use correct python-semantic-release/publish-action #3211

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 1 commit into from
Jul 8, 2025

Conversation

JohnVillalovos
Copy link
Member

The previous 'python-semantic-release/upload-to-gh-release' action has been deprecated.

Closes: #3210

@JohnVillalovos JohnVillalovos requested a review from nejch June 7, 2025 16:15
@JohnVillalovos JohnVillalovos force-pushed the jlvillal/psr_publish branch from 6de991e to 4402795 Compare July 7, 2025 18:14
Copy link
Member

@nejch nejch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @JohnVillalovos we might need to change some config if this fails again but LGTM!

The previous 'python-semantic-release/upload-to-gh-release' action has
been deprecated.

Closes: #3210
@nejch nejch force-pushed the jlvillal/psr_publish branch from 4402795 to a3e1423 Compare July 8, 2025 11:46
@nejch nejch enabled auto-merge (rebase) July 8, 2025 11:46
@nejch nejch merged commit 2f20634 into main Jul 8, 2025
29 of 30 checks passed
@nejch nejch deleted the jlvillal/psr_publish branch July 8, 2025 12:41
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.

python-semantic-release/upload-to-gh-release has been deprecated
2 participants