Unity CLI 1.0.0-beta.6

`unity bug` now requires you to be signed in, and exits with code `3` instead of `0` when you aren't. Previously a signed-out run reported nothing and appeared to succeed. Authenticate first, or pass service-account credentials, before a script or CI job calls `unity bug` .

`unity test` now uses exit code `8` specifically for a run whose tests failed. Every other way a test run fails to reach a verdict — a compile error, an expired license, an editor crash, or `--timeout` — keeps exit code `6` . If a script treats exit code `6` as "tests failed," point it at `8` instead.

`unity projects create` and `unity projects link vcs` can now create the new repository through `gh` , `glab` , or `tea` when the CLI's own REST clients can't reach the host: a GitHub Enterprise Server, a self-managed GitLab, or a self-hosted Gitea or Forgejo instance. `--vcs` accepts a bare hostname for these. No token passes through the CLI on this path; the provider CLI's own signed-in session does the work. A new `--git-description ` flag sets the repository's description.

`unity projects clone` and `unity projects link vcs` now accept a plain git URL — `ssh://` , `git@host:path` , or `https://` — as an optional positional argument, so any git host works, including Bitbucket, Azure DevOps, and a self-hosted server. This form uses your machine's own ambient git authentication rather than a provider API call.

Both commands, and `unity projects create --vcs` , now work fully over SSH, including host-key verification and passphrase-protected keys. Use `--git-remote-protocol ssh` on the flag form to switch the transport.

Signing in to github.com no longer implies anything on a self-hosted host. When a self-hosted or enterprise host needs its own sign-in, the CLI now names the exact command to run for whichever provider CLI you have installed.

Git credential prompts no longer hang. Without a terminal, in CI, under a machine-readable `--format` , or with `--non-interactive` , the CLI now fails immediately with exit code `4` naming the credential it needed, instead of waiting on a prompt nobody could answer.

Git operations under `unity projects` now respect your own git configuration ( `core.sshCommand` , `includeIf` rules, credential helpers) instead of ignoring it, and credential lookups resolve per organization when your credential helper supports it (set `git config --global credential.useHttpPath true` to opt in).

Added `unity projects verify` , a fast check for the things version control breaks in a Unity project: orphaned or missing `.meta` files, duplicate GUIDs from a bad merge, and unresolved conflict markers. It needs no Editor, license, or network access, so a broken checkout fails in seconds instead of after a full build. Pass `--strict` to fail on warnings too, and `--expect-editor ` to also check for editor-version drift.

`unity build` now writes a build provenance manifest next to its output, recording the editor version, resolved package set, build target, git revision, and timestamps that produced the build. It's written for failed builds too. Paths, credentials, and machine-identifying details are deliberately left out, so it's safe to publish alongside the artifact. Use `--provenance-path` to choose where it's written, or `--no-provenance` to turn it off.

`unity build` now prints a periodic heartbeat during a long build, tracking both elapsed time and how long since the editor's log last grew, so silence in the log no longer looks the same as a hang. A new `--timeout ` flag (also `UNITY_BUILD_TIMEOUT` ) aborts a build that runs too long.

`unity collaboration` ( `unity collab` for short) is now part of every build, instead of development builds only. It covers Unity Collaboration's annotations end to end — create, list, update, resolve, reply, and react — plus attachments, thumbnails, and a Jira integration that creates and links issues from the CLI. Run `unity collab --help` for the full command tree.

Added `--format github` , a global output format that reports command failures as GitHub Actions annotations instead of plain text, so a red step in a workflow points at what went wrong in its summary.

Added `unity cache key` , which prints a deterministic cache key for a Unity project's `Library` folder, derived from the editor version, the resolved package set, and the build target. Use it as the key for a CI cache step.

Added `unity doctor --ci` , a fast preflight that checks whether a machine can actually finish a build or test run — an activatable license, the project's required editor, disk space, and network reachability — and exits non-zero when it can't, so a pipeline fails in seconds instead of partway through a build.

`unity test` gained `--shard N/M` to split a suite deterministically across parallel CI jobs, `--retries N` to re-run only the tests that failed and report which ones were flaky, and `--rerun-failed` to re-run just the failures from a previous run's report.

Shell completion scripts ( `unity completion bash` , `fish` , and `powershell` ) now escape the strings they interpolate, closing a defense-in-depth gap where an unescaped value could have run as a command or broken out of its quoting.

Progress spinners and the background update check are hardened against a tampered update manifest smuggling terminal control sequences into the spinner label.

Editor and module install progress bars are back in the terminal. A large download previously printed nothing at all until it finished, which looked indistinguishable from a hang.

A stale Unity Licensing Client is now detected and replaced automatically, instead of silently rejecting every `unity license` command until it was deleted by hand.

The Android module on Linux, the Android NDK on macOS, Windows modules that need administrator elevation, and language packs all had install paths that were broken outright; all are fixed.

• Windows
• macOS
• Linux
• Android

Headless or wrapped editors (running under `xvfb-run` , `dbus-run-session` , or a CI runner) are counted correctly again by `unity status` , instead of appearing as duplicates or "ambiguous."

The loop where signing in with `unity auth login` eventually signed you out of the Unity Hub is fixed for good.

Installing the CLI on Windows no longer corrupts your user `PATH` . PowerShell tab completion now actually registers (it never took effect before). `unity command` now catches malformed or misspelled arguments instead of silently running on default values.

• Windows