Updates to build and release toolchain #17
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hej! It has been a long time since the latest release to PyPI (as noted by #12 (comment)). I guess there can be thousands of good reasons for that, but if "the boring process of doing it manually" is one of those reasons, this PR might have the fix :)
This PR:
setup.pyandMANIFEST.inwith the new and fancypyproject.toml.hatchfor building andhatch-vcsfor automatic versioning based on git tags.vX.Y.Ztag is created on GitHub.How to make it work
If this is interesting, the following steps need to be carried out for the magic to work.
On the GitHub repo
clicumu/pyDOE2, apypienvironment must be created:The default settings should work just fine.
On PyPI, the package must have the GitHub repo/environment set as a trusted publisher, see an example from one of my repos and what to fill in under Add a new publisher:
After this, it should probably work just fine when creating a new GitHub release with a version tag, e.g.,
v1.2.2. See the faux release on my fork and the resulting workflow run (failing because I obviously can't publish topyDOE2on PyPI).Let me know if I can help, or make any adjustments!
Fridens liljor!