v0.40.2
v0.40.2 (2026-03-03)
Bug Fixes
- fix: propagate profile workspace default to all command modules
The config 'workspace' setting in profiles was stored but never applied across the majority of CLI commands. Only ~11 of ~54 workspace-aware call sites used the profile fallback.
Add get_effective_workspace() helper in workspace_utils.py that returns the explicit workspace value or falls back to get_default_workspace() from the active profile. Apply this helper across all workspace-aware commands in 14 click modules covering all four resolution paths: resolve_workspace_filter, resolve_workspace_id, get_workspace_id_with_fallback, and validate_workspace_access.
Design decisions: - List/filter operations: profile default applied unconditionally - Create operations: profile default applied when no workspace given - Update operations: profile default NOT applied (would silently move resources to another workspace without explicit user intent) - Import-from-file: profile default applied only when workspace is absent from both CLI flag and JSON file
Also add/update unit tests and autouse fixtures to prevent Also add/update unit tests and autouse fixtures to prevent Also add/upssertions.
- feat: add --workspace all sentinel to bypass profile default filter
What's Changed
- fix: propagate profile workspace default to all command modules by @fredvisser in #75
Full Changelog: v0.40.1...v0.40.2
