ci: publish to PyPI (OIDC) and crates.io on release tags#28
Merged
Conversation
rafaelperoco
force-pushed
the
chore/pypi-crates-publish-jobs
branch
from
e822811 to
bca2e2a
Compare
52 tasks
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.
Closes part of #13.
Adds two jobs to
release.ymlso that pushingvX.Y.Zalso publishes:pypideployment environment.CRATES_TOKENrepo secret. Job no-ops with a clear message when the secret is absent.The pre-release tag form (
v2.0.0-alpha.1) is translated to PEP 440 (2.0.0a1) beforepyproject.tomlis rewritten — semver pre-release suffixes are not valid PEP 440. cargo accepts SemVer 2.0 directly so no translation is needed.CONTRIBUTING.md gains a registry table documenting the one-time setup for each registry. The first publish on each must be done manually to reserve the name; subsequent publishes ride this pipeline.