Repository navigation
ci: read the crates.io token from CRATES_PUBLISHING_TOKEN - #7
Merged
Merged
Conversation
The organization's publishing secret is CRATES_PUBLISHING_TOKEN; cargo still reads it as CARGO_REGISTRY_TOKEN.
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.
The crates-io job read
secrets.CARGO_REGISTRY_TOKEN, which doesn't exist, so the v0.1.4 release failed with "please provide a non-empty token". The organization's secret isCRATES_PUBLISHING_TOKEN; cargo still gets it asCARGO_REGISTRY_TOKEN.After merging, re-release v0.1.4 with the workflow's
taginput (gh workflow run ci.yml -f tag=v0.1.4). The crates-io job then publisheszk-encryption 0.1.4and the GitHub release follows. The CDN assets are already published.