Bug 1879869 - Document how to manually publish Rust crates in the release docs #3035
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
travis79
approved these changes
Jan 6, 2025
Comment on lines
+224
to
+230
| ### Manual release | ||
| If any of the package releases fail for some other reason it might be possible to manually publish the package, using the same commands being run on CI. | ||
| #### Manual release: Rust crates | ||
| Make sure you're logged in to `crates.io`: |
There was a problem hiding this comment.
Well... if you have the proper access. Since I doubt anyone but us would need to do a manual release, this is probably fine as is, but it might not hurt to mention that you need to be an owner at the deployment site (pypi, crates.io, etc)
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.
[doc only]