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.

1 files changed, 1 insertions, 1 deletions

diff --git a/crates/shirabe/src/plugin/plugin_manager.rs b/crates/shirabe/src/plugin/plugin_manager.rs
index 1ecb4153..04c53d08 100644
--- a/crates/shirabe/src/plugin/plugin_manager.rs
+++ b/crates/shirabe/src/plugin/plugin_manager.rs
@@ -1221,7 +1221,7 @@ impl PluginManager {
         if rules.is_none() {
             if !self.io.is_interactive() {
                 self.io.write_error("<warning>For additional security you should declare the allow-plugins config with a list of packages names that are allowed to run code. See https://getcomposer.org/allow-plugins</warning>");
-                self.io.write_error("<warning>This warning will become an exception once you run composer update!</warning>");
+                self.io.write_error("<warning>This warning will become an exception once you run shirabe update!</warning>");
 
                 let mut m: IndexMap<String, bool> = IndexMap::new();
                 m.insert("{}".to_string(), true);