Configure release to PyPI and Homebrew #48
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
m-dzianishchyts
force-pushed
the
cd-pypi
branch
from
4e4d984
to
8775613
Compare
m-dzianishchyts
force-pushed
the
cd-pypi
branch
from
3c95968
to
1185f15
Compare
m-dzianishchyts
changed the title
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.
What does this PR do?
Configures release to PyPI and Homebrew.
Slightly refactors release workflow.
Closes #45.
Closes #46.
Details
The workflow is required to be added to trusted publishers in the PyPI project settings to make a release to PyPI.
The workflow requires personal
HOMEBREW_RELEASE_ACCESS_TOKENto be provided in this repository with Contents (read and write) access to https://github.com/dflib/jjava and https://github.com/dflib/homebrew-tap to make a release to Homebrew.Testing
https://github.com/m-dzianishchyts/jjava/actions/runs/11243616031