Unity CLI: стари версии за изтегляне

Highlights of 1.0.0-beta.14 (full notes at the release notes URL):
- unity config path prints where the CLI keeps its configuration: the settings file and the directory that holds it.
- unity terms accept <version> accepts the Unity Editor Software Terms for an installed Editor, so it opens without the "Unity Editor Software Terms" dialog, as a container or provisioning script needs.
- The CLI now recognizes when GitHub Copilot runs it, from VS Code's agent terminal or the Copilot CLI.
- unity releases --operating-system <windows|macos|linux> lists another operating system's releases, and unity install <version> --dry-run --operating-system <os> shows what that system's Editor and modules would download, so you can plan a Windows build machine from a Mac.
- When the CLI is signed out and Unity Hub is signed in, unity auth login shows the Hub's account and the unity auth switch command that uses it in the CLI with no browser sign-in, then continues with the browser sign-in.
- unity open --until-ready (and unity projects open --until-ready) now names three dialogs the way unity status does: OPEN_BLOCKED_BY_DIALOG_SAFE_MODE for "Enter Safe Mode?" (quoting up to three compile errors from the Editor's log), OPEN_BLOCKED_BY_DIALOG_GRAPHICS_API for the Windows "Auto Graphics API Notice", and OPEN_BLOCKED_BY_DIALOG_SOFTWARE_TERMS for "Unity Editor Software Terms".
- unity status reports an Editor waiting at the "Enter Safe Mode?" prompt with its own error code, STATUS_BLOCKED_BY_DIALOG_SAFE_MODE, and quotes the first compile errors from the Editor's log when it can read them.
- unity cloud project --help now ends with a pointer to unity projects link cloud, where a local project is linked to Unity Cloud, and unity projects link cloud --help points back to unity cloud project for listing projects and setting a default.

Highlights of 1.0.0-beta.13 (full notes at the release notes URL):
- unity mcp now reads UNITY_PROJECT_PATH when you don't pass --project-path, the way unity command, list, job and status already do.
- unity setup codex and unity setup grok install Unity's agent plugin, with its Unity skills, into Codex and Grok Build in one step, the way unity setup claude does for Claude Code.
- On a Mac with Apple silicon running macOS 28 or later, unity releases no longer lists Intel (x86_64) Editor builds, which can't run without Rosetta 2. Earlier macOS versions still list both, as unity install and unity editors upgrade already did.
- unity projects upgrade into Unity 6.7 or later now needs a Unity Cloud choice when the project isn't linked: --cloud links it to a new Unity Cloud project, --cloud-project <id-or-name> links an existing one, and --no-cloud upgrades without linking.
- unity open and unity projects open no longer move a project onto Unity 6.7 or later.
- unity install with --changeset, and unity editors add and unity editor module refresh when they read an Editor's build from the download server, now refuse a changeset that is not letters and digits, and a manifest file name from the server that is not a plain file name.
- Setting UNITY_PEER_AUTH_MODE=identify-only no longer weakens your real sign-in: a broker started that way runs as a separate dev broker with its own address and its own sign-in, never reads yours, and on macOS and Windows refuses Unity-signed applications.
- The CLI now checks that the sign-in service it talks to is genuine Unity software and that it checks the apps that connect to it.

Highlights of 1.0.0-beta.12 (full notes at the release notes URL):
- unity projects create --with-pipeline adds the Pipeline package (com.unity.pipeline) to the new project, so an AI agent can drive the Editor as soon as it opens, without a separate unity pipeline install.
- unity status --format json shows whether a game in Play mode is actually running.
- unity install, unity install-modules and unity projects require accept --no-wait and --wait-timeout <seconds> for when the Hub or another CLI is already installing.
- Experimental, unsupported: on a Linux arm64 host you can opt in to running the x86_64 Unity Editor under FEX-Emu by setting UNITY_EXPERIMENTAL_FEX_EMU=1.
- A registry plugin's published version can now state the minimum version of a runtime it needs.
- unity commands --grep <pattern> searches the CLI's commands and its plugin catalog by keyword, so you can find the command for a task without paging through --help.
- unity plugin list now shows a short description of what each plugin does, in every format (human, --format json, and --format tsv), whether or not it's installed.
- unity plugin install, unity plugin upgrade, unity plugin list and unity doctor now say where each runtime a plugin uses came from: machine for a copy that was already on your computer, package-manager for one installed through Homebrew, winget, apt or dnf, and managed for the Unity CLI's own download.

Highlights of 1.0.0-beta.11 (full notes at the release notes URL):
- unity recompile checks that your scripts compile in a running Editor, without a full build.
- unity docs <topic> opens the Unity documentation for a class or topic, matched to your project's Unity version.
- unity assets import <file.unitypackage> imports a .unitypackage into a project.
- unity assets export <asset-path...> --output <file.unitypackage> exports assets and folders to a .unitypackage.
- unity cloud org create <name> creates a Unity Cloud organization.
- unity pipeline cloud-build and unity pipeline automation list and inspect Unity Build Automation targets and builds, and Unity Pipeline Automation apps, pipelines, and jobs.
- unity mcp configure --server issue-tracker adds the Unity Issue Tracker MCP server to your AI client.
- unity run --log-file <path> writes the Editor log to a file, including with --command, and streams it to the console like unity build.

Highlights of 1.0.0-beta.10 (full notes at the release notes URL):
- Security: unity mcp configure no longer follows a symlinked path component when writing a client's config file, confining a --local write to the project directory and closing an arbitrary-file-overwrite gap a malicious cloned repo could trigger. Every client config write is now atomic.
- Security: unity mcp configure --dry-run no longer prints your whole existing MCP config file, which is exactly where per-server credentials live.
- Security: the resident auth broker now signs every refresh-token request with a DPoP (RFC 9449) proof, and both its signing key and its token store are hardware-backed where the machine supports it: TPM on Windows and Linux, Secure Enclave on macOS.
- Security: the Editor identity daemon and the auth broker now verify a connecting peer's code signature before serving it on macOS and Windows, and on macOS the CLI no longer ad-hoc re-signs a downloaded plugin or component whose signature fails to verify.
- unity context defines named bundles of the five defaults you otherwise set one command at a time: active account, default organization, cloud project, editor and install path.
- unity commands emits the CLI's own command tree as a machine-readable manifest, and unity vcs blame reports who last changed each GameObject and component in a scene or prefab, with commit, author and date.
- Unity Accelerator support: unity config accelerator <host:port> persists an import-cache endpoint that unity run, unity test and other commands reuse instead of retyping it per invocation.
- Build discovery and iteration: unity build gains --create-profile, --list-targets and --list-profiles, and unity build run relaunches the most recent successful build without rebuilding.
- unity watch test re-runs unity test --affected on every project change, and a committed ProjectSettings/UnityCliConfig.json declares unity build and unity test defaults once for a whole repository.
- Fixes include Editor discovery from WSL against an Editor on the Windows host, Editors briefly reported unreachable after a recompile, git misreported as missing on Windows on Arm, and self-update and self-install on Windows when a resident helper holds the binary open.

Highlights of 1.0.0-beta.9 (full notes at the release notes URL):
- unity version is a new command that prints the CLI's version, release channel, commit, platform and runtime in any output format, and unity --version now honors --format.
- unity test --affected --since <ref> runs only the tests a change can reach, taken from unity vcs affected's guid impact graph rather than a hand-written filter.
- unity config get|set|list|unset <key> reads and writes the CLI's persistent settings by key, instead of a separate command per setting.
- A --color auto|always|never global flag, with --no-color as shorthand, controls colored output on every command and takes precedence over NO_COLOR and FORCE_COLOR.
- The auth broker's token store is now sealed to the machine that wrote it — TPM on Windows and Linux, Keychain on macOS — so the file on disk is worthless anywhere else.
- unity plugin changelog <id> shows a managed tool's own release notes, and unity doctor now lists the CLI's bundled third-party components with their SPDX licenses.
- Module options are renamed for consistency: unity install --list-components is now --list-modules, and --childModules is now --child-modules. The old spellings keep working.
- On Windows, unity pipeline list and unity status no longer report that no Editor is running when one is, and now say when they could not check. unity doctor no longer hangs on macOS when the keychain wants to ask you something.

Highlights of 1.0.0-beta.8 (full notes at the release notes URL):
- unity close closes the Unity editor that has a project open, and is available in a released build for the first time. Neither the default nor --force saves your work.
- The command that updates the CLI itself is now unity self-update; unity upgrade keeps working as an alias.
- Repository creation now works on Bitbucket through bkt and on Azure DevOps through az, alongside the existing gh, glab, and tea integrations.
- On Windows, unity install no longer reports a successful install as failed when you are not an administrator, and installing modules into a protected folder now works.
- Interrupting a download with Ctrl+C no longer leaves the taskbar showing progress forever, orphans the elevated installer, or leaves the install lock behind.
- Commands no longer stall after their work is done on a signed-in, opted-in profile, where reading the OS keyring could block for tens of seconds.
- unity vcs uvcs review reads and answers Unity Version Control code review comments from the terminal.

Highlights of 1.0.0-beta.6 (full notes at the release notes URL):
- unity projects create and unity projects link vcs can now create the repository through gh, glab, or tea for hosts with no REST client: GitHub Enterprise Server, self-managed GitLab, self-hosted Gitea/Forgejo.
- unity projects clone and unity projects link vcs accept a plain git URL now, including full SSH transport, so any git host works.
- unity projects verify is a new command that checks a project for broken .meta files, duplicate GUIDs, and unresolved merge conflicts without needing an Editor or a license.
- unity build now writes a redacted build provenance manifest next to its output and prints a periodic stall heartbeat, with a new --timeout flag.
- unity collaboration (unity collab) is part of every build now instead of development builds only.
- unity test gains --shard, --retries, and --rerun-failed for CI, and now uses exit code 8 specifically for failing tests, reserving 6 for a run that never reached a verdict.

Highlights of 1.0.0-beta.5 (full notes at the release notes URL):
- unity bug no longer uploads your account name or email address. The log file it attaches records home-directory paths on nearly every line, so on a machine where the account name is your real name, submitting a report sent it. Both are now redacted as each line is written. Logs written before this release are unaffected.
- A retried module download in unity install-modules resumes the partial file it already has instead of restarting, so a module that fails and succeeds within one run leaves a single file instead of one numbered file per attempt.
- unity build, unity test, and unity run now report an Editor killed by a signal as "stopped with signal SIGSEGV" instead of "exited with code 1".
- Routine outcomes stopped suggesting you report a CLI bug: declining a module's license terms, a failing build, and an install waiting on another install's lock are situations, not faults. Messages, exit codes, and the --format json envelope are unchanged.
- unity --help shows the Unity logo header again.
- unity completion zsh now produces a script that registers itself with zsh, so Tab completes commands, subcommands, and flags.

Highlights of 1.0.0-beta.3 (full notes at the release notes URL):
- unity run --command executes a registered Editor command headlessly in one invocation.
- unity shell gains persistent history, tab completion, session context/defaults, and a framed NDJSON machine protocol for agents.
- unity editors running lists running Editor instances and their open projects; unity projects size reports per-folder disk usage.
- unity bug can run fully non-interactively via flags; UNITY_NO_CONSENT_PROMPT suppresses the first-run analytics prompt for wrapper scripts.
- Install/download progress reports to the terminal taskbar via OSC 9;4; unity upgrade now updates AppImage installs in place.
- Crash reporting via Sentry (anonymous, scrubbed; disable with UNITY_NO_CRASH_REPORT) and expanded opt-in usage analytics.