Prepare mdbook-spec for publishing #62
Merged
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
ehuss
force-pushed
the
mdbook-spec-publish-ready
branch
2 times, most recently
from
1913889 to
15fbc70
Compare
ehuss
force-pushed
the
mdbook-spec-publish-ready
branch
from
15fbc70 to
f8387c6
Compare
JoelMarcey
approved these changes
Jun 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In order to fit the extension into the rust release process, we'll need to publish this extension onto crates.io. Ideally this would just get pulled in with the submodule, but some people don't like that. It's a bit unfortunate, since it will make it a bit more difficult to make updates (requiring publishing mdbook-spec and then separately updating the version in rust-lang/reference).
I'll follow up with automation for publishing new versions via GitHub Actions.