Skip to content

fix(tag): add multi-module workspace support#209

Merged
indaco merged 2 commits intomainfrom
fix/tag-multimodule-support
Feb 11, 2026
Merged

fix(tag): add multi-module workspace support#209
indaco merged 2 commits intomainfrom
fix/tag-multimodule-support

Conversation

@indaco
Copy link
Copy Markdown
Owner

@indaco indaco commented Feb 11, 2026

Description

Fixes a bug where sley tag create, sley tag push, and sley tag list commands fail in multi-module projects with the error open .version: no such file or directory.

Changes Made

  • Added multi-module flags (--all, --module, --modules, --pattern) to the tag command via cliflags.MultiModuleFlags()
  • Implemented resolveVersionPath() function that uses clix.GetExecutionContext to properly detect and handle multi-module workspaces
  • Updated runCreateCmd and runPushCmd to call resolveVersionPath() instead of getVersionPath()
  • Added interactive TUI module selection - in multi-module mode without --all/--module flags, users are prompted to select which module's version to tag

Behavior

Single-module projects: Works exactly as before (backward compatible)

Multi-module projects:

  • Interactive mode: Shows TUI prompt to select which module's version to use
  • --all flag: Auto-selects first module (no prompt)
  • --module <name> flag: Uses specified module's version
  • Prints which module the version was sourced from for transparency

Related Issue

Fixes #208

Notes for Reviewers

  • None

@indaco indaco merged commit c3a259b into main Feb 11, 2026
4 checks passed
@indaco indaco deleted the fix/tag-multimodule-support branch February 11, 2026 22:19
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.

tag create and tag push commands in multi-module workspace -> failed to read version from .version

1 participant