Skip to content

Commit

Permalink
Revert "Try a new (less confusing?) message explaining the rename sit…
Browse files Browse the repository at this point in the history
…uation (#1462)" (#1493)

This reverts commit ccd01af.
  • Loading branch information
msullivan authored Feb 23, 2025
1 parent e916d24 commit e6bebb5
Showing 1 changed file with 2 additions and 12 deletions.
14 changes: 2 additions & 12 deletions src/cli/install.rs
Original file line number Diff line number Diff line change
Expand Up @@ -648,19 +648,9 @@ pub fn check_executables() {
log::debug!("new_executable: {new_executable:?}");

if exe_path.file_name().unwrap() == BRANDING_CLI_CMD_ALT_FILE {
// TODO: When we are ready to release a stable renamed
// version, remove this message and turn on the one below.
log::warn!(
"EdgeDB is in the process of being renamed to {BRANDING}. \
This nightly version of the CLI reflects that. We apologize for \
any confusion or inconvenience. \
This warning may be silenced by running the new \
`{BRANDING_CLI_CMD_FILE}` executable."
);

if new_executable.exists() {
// log::warn!("`{exe_path:?}` is the old name for the `{BRANDING_CLI_CMD_FILE}` executable. \
// Please update your scripts (and muscle memory) to use the new executable at `{new_executable:?}`.");
log::warn!("`{exe_path:?}` is the old name for the `{BRANDING_CLI_CMD_FILE}` executable. \
Please update your scripts (and muscle memory) to use the new executable at `{new_executable:?}`.");
} else {
log::warn!(
"`{exe_path:?}` is the old name for the `{BRANDING_CLI_CMD_FILE}` executable, but \
Expand Down

0 comments on commit e6bebb5

Please sign in to comment.