chore: homogenize crate versions to 0.1.0 (#515) - #639
Merged
Conversation
Hoist version = "0.1.0" into [workspace.package] and switch every core crate (nexum/videre/shepherd groups plus tools) to version.workspace = true. Four crates (shepherd, nexum-runtime, nexum-launch, nexum-cli) carried a drifted 0.2.0 that corresponds to no git tag, release, or inter-crate version pin; the rest were already 0.1.0. Guest modules under modules/ keep an explicit 0.1.0 (a module author has no access to the workspace table). Cargo.lock regenerated: a single 0.1.0 across the workspace. Closes #515.
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.
Hoist
version = "0.1.0"into[workspace.package]and switch every core crate (nexum/videre/shepherd groups + tools) toversion.workspace = true. Four crates (shepherd,nexum-runtime,nexum-launch,nexum-cli) carried a drifted0.2.0corresponding to no tag/release/pin; the rest were already0.1.0. Guest modules undermodules/keep an explicit0.1.0(a module author has no access to the workspace table).Validation
cargo metadatashows a single0.1.0across the workspace (modules included).cargo check --workspace --all-features --locked: green;Cargo.lockregenerated (only the 4 version bumps).Closes #515.