ci: transition to jh-org typical release workflow #269
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.
We have successfully started using PyPI's temporary credentials that can be granted from a GITHUB_TOKEN from a github workflow to make a release to PyPI assuming the project is pre-configured to trust a specific workflow in a github repository (release.yaml).
Should we transition to using that system in this project also perhaps? Then we can remove the PYPI_TOKEN github repository secret as well etc.
Action points
Related org wide discussion