github actions: update/fix publish to PyPI workflows #1572
Merged
Conversation
This file contains 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
joergsteffens
force-pushed
the
dev/joergs/master/publish-pypi-update
branch
from
20523b2
to
1d275d4
Compare
joergsteffens
force-pushed
the
dev/joergs/master/publish-pypi-update
branch
2 times, most recently
from
78f9a7f
to
5e16274
Compare
arogge
approved these changes
Nov 3, 2023
This was referenced Nov 3, 2023
Update the python packages publishing process. Only use one workflow, instead of 4. Update the used actions and changed authentication for PyPI from TOKEN to Trusted Publishing.
BareosBot
force-pushed
the
dev/joergs/master/publish-pypi-update
branch
from
a7e50f4
to
113a462
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The latest builds fail to publish to (test.)pypi.org.
This PR adapts the versioning again and updates the used github actions to the current stable versions.
Please check
If you have any questions or problems, please give a comment in the PR.
Helpful documentation and best practices
Checklist for the reviewer of the PR (will be processed by the Bareos team)
Make sure you check/merge the PR using
devtools/pr-toolto have some simple automated checks run and a proper changelog record added.General
Source code quality