Unity CLI 1.0.0-beta.5

`unity bug` no longer uploads your account name or email address. The CLI's log file records paths under your home directory on nearly every line, and a bug submission attaches that file as-is, so on a machine where the account name is your real name, submitting a report sent it too. Both are now redacted as each line is written: the account name becomes `` wherever it appears, and email addresses become `` . Nothing else about the line changes, so an install failure stays diagnosable. Logs written before this release are unaffected; delete them if you'd rather not send them.

A retried module download in `unity install-modules` now resumes the partial file it already has instead of starting that module again from the beginning. A module that failed and then succeeded within the same run previously left one numbered file per attempt, such as `android (1).pkg` and `android (2).pkg` ; it now leaves a single file and downloads its bytes once. The retry count and the exit code are unchanged.

• Android

`unity build` , `unity test` , and `unity run` now report an Editor killed by a signal as `stopped with signal SIGSEGV` , naming the signal, instead of reporting `exited with code 1` . `SIGILL` , `SIGTRAP` , `SIGFPE` , and `SIGBUS` are recognized too, where they previously surfaced as a bare number such as 132. An Editor that exits normally still reports its own exit code.

Routine outcomes no longer suggest you report a CLI bug. Declining a module's license terms, being told to pass `--accept-eula` in a non-interactive shell, running `unity modules ` for an Editor you haven't installed, setting an invalid path with `unity install-path --set` , a `unity build` whose build fails, and a `unity install` that waits on another install's lock all stopped printing "Run `unity bug` to report this issue". The messages, the exit code (6), and the `--format json` envelope, including the `BUILD_FAILED` error code, are unchanged, so scripts that branch on them keep working. An Editor that crashes mid-build is still reported as a fault.

`unity --help` , `unity -h` , `unity help` , and bare `unity` show the Unity logo header again. The header still stays out of the way when you pipe the output, pass `--quiet` or `--no-banner` , or ask for a machine-readable format, and subcommand help such as `unity install --help` is unchanged.

`unity completion zsh` now produces a script that registers itself with zsh, so pressing Tab completes commands, subcommands, and flags. The script previously defined the completer without telling zsh about it, and Tab fell back to plain filename completion with no error to explain why. Save it to a directory on your `$fpath` : mkdir -p ~/.zsh/completionsunity completion zsh > ~/.zsh/completions/_unity Then make sure your `~/.zshrc` has `fpath=(~/.zsh/completions $fpath)` followed by `autoload -Uz compinit && compinit` . bash, fish, and PowerShell completion are unaffected.

The `--proxy` help text shows its credentialed example as `http://:@host:8080` , so it's clear which parts you substitute. In Spanish, the username in that example is no longer mistranslated.