From ec5f3292ac324789298c3a12972f8f78b688ca24 Mon Sep 17 00:00:00 2001 From: nsfisis Date: Sat, 22 Aug 2026 17:53:13 +0900 Subject: feat(cli): tell the user to run `shirabe`, not `composer` Messages that instruct the user to run a command named the Composer binary. Shirabe ships as its own binary, so the hints now name it. File names (composer.json, composer.lock), the "composer" repository type and prose about Composer itself are untouched. The installer and functional integration fixtures live in the Composer submodule and cannot be edited, so their expected output is normalized on load. --- crates/shirabe/src/command/validate_command.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crates/shirabe/src/command/validate_command.rs') diff --git a/crates/shirabe/src/command/validate_command.rs b/crates/shirabe/src/command/validate_command.rs index d460ea6c..16d3b4d0 100644 --- a/crates/shirabe/src/command/validate_command.rs +++ b/crates/shirabe/src/command/validate_command.rs @@ -306,7 +306,7 @@ impl Command for ValidateCommand { let locker = composer.get_locker().clone(); let mut locker = locker.borrow_mut(); if locker.is_locked() && !locker.is_fresh()? { - lock_errors.push("- The lock file is not up to date with the latest changes in composer.json, it is recommended that you run `composer update` or `composer update `.".to_string()); + lock_errors.push("- The lock file is not up to date with the latest changes in composer.json, it is recommended that you run `shirabe update` or `shirabe update `.".to_string()); } if locker.is_locked() { -- cgit v1.3.1-4-g156e