fix: use crate name dakera-cli in install-test workflow (not binary name dk)#87
Merged
Conversation
…rew tests Two fixes: - publish-linux-packages.yml: rm -rf target/debian/ and target/generate-rpm/ before building. A cache hit on `target/` left the old `dakera-cli_*.deb` alongside the new `dk_*.deb`; head -1 in the publish step picked the wrong one alphabetically. Clearing ensures only the freshly-named package exists. - install-test.yml: remove continue-on-error from brew jobs now that homebrew-tap is public (DAK-5437 resolved). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ame dk) cargo install and cargo binstall require the crate name, not the binary name. The crate is published as dakera-cli on crates.io and installs the dk binary. Also removes continue-on-error and the stale DAK-5436 NOTE comment now that dakera-cli v0.6.0 is live on crates.io. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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.
Summary
cargo install dk→cargo install dakera-cli(crate name, not binary name)cargo binstall dk→cargo binstall dakera-clicontinue-on-error: truefrom both jobs — dakera-cli v0.6.0 is live on crates.ioRoot Cause
Platform wrote the original workflow using the binary name (
dk) instead of the crate name (dakera-cli).cargo installandcargo binstallrequire the crate name; the binary name is what gets installed to PATH.Verification
cargo install dakera-cli --lockedandcargo binstall dakera-cli --no-confirmwill resolve correctly nowTest plan
test-cargo-installandtest-cargo-binstallboth passCloses DAK-5443 / DAK-5442
🤖 Generated with Claude Code