Skip to content

Conversation

@joshrotenberg
Copy link
Collaborator

Summary

Final fix for the 'no packages selected' error - adding default-members to workspace configuration.

Problem

cargo-release reports 'no packages selected' even with --workspace flag.

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 --workspace flag alone isn't enough in some configurations.

Solution

Add default-members to the workspace configuration:

[workspace]
members = [
    "crates/redis-cloud",
    "crates/redis-enterprise",
    "crates/redisctl",
]
default-members = [
    "crates/redis-cloud",
    "crates/redis-enterprise",
    "crates/redisctl",
]

This explicitly tells cargo-release which packages to operate on.

Why This Works

  • members defines what's in the workspace
  • default-members defines what to operate on by default
  • With this configuration, cargo-release knows to release all three packages
  • This works with or without the --workspace flag

This is the final piece of the puzzle for getting releases working!

The 'no packages selected' error occurs because cargo-release
needs to know which packages to operate on in a workspace.

Adding default-members tells cargo (and cargo-release) which
packages to operate on when no specific package is selected.

This should finally fix the release workflow.
@joshrotenberg joshrotenberg merged commit 1198e98 into main Sep 9, 2025
12 checks passed
@joshrotenberg joshrotenberg deleted the fix/workspace-default-members branch September 9, 2025 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants