Release 0.2.13 with the dual license - #986
Merged
Merged
Conversation
Publish the dual-license choice through Cargo packages, native archives, the wasm artifact and the official MCP Registry metadata. Keep the package license ratchet exact across platforms by comparing normalized text rather than checkout line endings. Closes #985 Co-authored-by: GitHub Copilot <copilot@github.com>
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
The repository is dual licensed, but immutable crates.io 0.2.12 metadata still advertises Apache-2.0 only. This cuts 0.2.13 across the workspace, lock, README transcript and official MCP Registry manifest.
Closes #985.
Why this way
A patch release makes the license choice reach actual package consumers without waiting for an unrelated language change. The package ratchet also normalizes CRLF to LF before comparing license texts, so a Windows checkout cannot turn identical packaged licenses into a false failure.
What it still does not do
This PR does not publish by itself. The signed tag, GitHub release assets, 20 crates.io packages, Registry entry and website pin follow after merge.
Checks
cargo fmt --all -- --checkcargo clippy --workspace --all-targets -- -D warningscargo nextest run --workspace --profile ci --no-fail-fast(2523 passed, 4 skipped)cargo test --doc --workspace(11 passed)cargo test -p deed-driver --test publishing(5 passed)cargo test -p deed-lang --test registry(1 passed)cargo test -p deed-driver --test documentation(31 passed, 1 ignored)cargo publish --workspace --dry-run --locked(20 packages)deed --versionreports 0.2.13