Close the crates.io version gap - #976
Merged
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
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.
What this changes
All twenty Deed packages are now published at 0.2.10, matching the GitHub release. The roadmap no longer says the two installation paths produce different compilers.
Why this way
Publishing was done from the exact v0.2.10 tag in dependency order. The result was checked through the crates.io API for all twenty packages and by installing
deed-lang 0.2.10into an empty root, then runningdeed --version,deed newand the generated project's tests.What it still does not do
Tagging still does not automatically publish crates.io packages. That release automation decision remains separate.
Checks
deed 0.2.10AI assistance: GitHub Copilot implemented and verified this change.