chore(release): realign 4 satellite crates + harden release.sh dry-run#65
Merged
Conversation
Bump toolpath-dot 0.1.2→0.1.3, toolpath-md 0.2.0→0.2.1, toolpath-git
0.1.3→0.1.4, toolpath-github 0.2.0→0.2.1. No source changes — these
crates were last released when toolpath was at 0.1.5, so their
on-registry manifests still pin that old version. Without these
bumps, publishing path-cli (which depends on toolpath = "0.2.0"
and toolpath-dot = "0.1.2") drags two majors of toolpath into
cargo's publish-time resolution, producing E0308 type mismatches.
The new versions inherit the workspace's current toolpath = "0.2.0"
via toolpath = { workspace = true }, closing the skew.
scripts/release.sh now defaults to dry-run; pass --execute to publish
for real. Confirmation prompt and dirty-tree check only apply under
--execute. After the existing test/clippy/doc preflight, a new
publish-resolution dry-run loop runs `cargo publish --dry-run` for
every crate slated to publish. Failures referencing another
to-be-published crate are deferred (chicken-and-egg); any other
failure aborts before real upload. Recognizes three cargo error
shapes: "no matching package named", "failed to select a version
for the requirement", and "could not find ... in registry".
Verified end-to-end that path-cli's dry-run currently extracts
toolpath-dot as the deferred dep.
|
🔍 Preview deployed: https://ea53b630.toolpath.pages.dev |
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.
Bump toolpath-dot 0.1.2→0.1.3, toolpath-md 0.2.0→0.2.1, toolpath-git 0.1.3→0.1.4, toolpath-github 0.2.0→0.2.1. No source changes — these crates were last released when toolpath was at 0.1.5, so their on-registry manifests still pin that old version. Without these bumps, publishing path-cli (which depends on toolpath = "0.2.0" and toolpath-dot = "0.1.2") drags two majors of toolpath into cargo's publish-time resolution, producing E0308 type mismatches. The new versions inherit the workspace's current toolpath = "0.2.0" via toolpath = { workspace = true }, closing the skew.
scripts/release.sh now defaults to dry-run; pass --execute to publish for real. Confirmation prompt and dirty-tree check only apply under --execute. After the existing test/clippy/doc preflight, a new publish-resolution dry-run loop runs
cargo publish --dry-runfor every crate slated to publish. Failures referencing another to-be-published crate are deferred (chicken-and-egg); any other failure aborts before real upload. Recognizes three cargo error shapes: "no matching package named", "failed to select a version for the requirement", and "could not find ... in registry". Verified end-to-end that path-cli's dry-run currently extracts toolpath-dot as the deferred dep.