Bump version to 2.0.0 and update pipelines to use trusted publishing #20
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
(for a newcomer it can look like they are expected inputs)
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.
There was a request to tag a non-beta version for the Python packaging changes, which were first tagged as a pre-release of 1.0.0. I noticed only now that version v1.0.0 had actually been tagged much earlier, so the new version should be v2.0.0 due to the backward-incompatible changes.
I already published the 2.0.0 release to PyPI from the Helsinki-NLP fork, so the PR is just to keep this repository in sync.
I also included the commit to the documentation from #19 in the 2.0.0 release, so it's enough to merge this PR.