fix: add default-members to workspace configuration #226
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
Final fix for the 'no packages selected' error - adding
default-membersto workspace configuration.Problem
cargo-release reports 'no packages selected' even with
--workspaceflag.Root Cause
In a Cargo workspace without
default-members, cargo-release doesn't know which packages to operate on when running from the workspace root. The--workspaceflag alone isn't enough in some configurations.Solution
Add
default-membersto the workspace configuration:This explicitly tells cargo-release which packages to operate on.
Why This Works
membersdefines what's in the workspacedefault-membersdefines what to operate on by default--workspaceflagThis is the final piece of the puzzle for getting releases working!