Skip to content

unity-cli@v3.0.2 - #81

Open
StephenHodgson wants to merge 8 commits into
mainfrom
dev/3.0.2
Open

unity-cli@v3.0.2#81
StephenHodgson wants to merge 8 commits into
mainfrom
dev/3.0.2

Conversation

@StephenHodgson

Copy link
Copy Markdown
Member
  • bump deps
  • fix Linux Hub install for Hub 3.20+ (/usr/lib/unityhub layout; keep legacy /opt/unityhub support)

- bump deps
- fix Linux Hub install for Hub 3.20+ (/usr/lib/unityhub layout; keep legacy /opt/unityhub support)

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR releases unity-cli@v3.0.2, updating dependencies and fixing Unity Hub installation/runtime path resolution on Linux to support Hub 3.20+’s /usr/lib/unityhub layout while retaining legacy /opt/unityhub support.

Changes:

  • Add Linux Hub executable path resolver that prefers UNITY_HUB_PATH, then /usr/lib/unityhub/unityhub, then /opt/unityhub/unityhub.
  • Update Linux apt repo bootstrap to use DEB822 .sources and remove the legacy .list file to avoid duplicate-source warnings.
  • Bump runtime/dev dependencies and lockfile for the v3.0.2 release.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

File Description
src/unity-hub.ts Adds Linux Hub path resolution + updates Linux install/update scripts for Hub 3.20+ layout.
tests/linux-hub-path.test.ts Adds unit tests validating Linux Hub executable resolution behavior.
package.json Bumps version to 3.0.2 and updates dependency versions.
package-lock.json Synchronizes lockfile with dependency/version bumps.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread src/unity-hub.ts Outdated
Hub 3.20 moves the binary from /opt to /usr/lib; a stale xvfb wrapper caused exit 127.
Windows hosted runners often hit WSAEACCES (10013); treat as benign in UTP assertions and log remapping.
Parse and classify once in normalizeTelemetryEntry so telemetry artifacts, summaries, and CI assertions share the same severity instead of re-special-casing messages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants