Skip to content

Upgrade Unity version to 6000.0.70f1#371

Merged
from2001 merged 2 commits intodevelopfrom
upgrade/6000.0.70f1
Mar 14, 2026
Merged

Upgrade Unity version to 6000.0.70f1#371
from2001 merged 2 commits intodevelopfrom
upgrade/6000.0.70f1

Conversation

@from2001
Copy link
Collaborator

This pull request updates the Unity project to use newer versions of several Unity packages and updates the project configuration to support these changes. It also switches the default solution file to a new .slnx format and adds the corresponding solution file. These changes help maintain compatibility with the latest Unity editor and package ecosystem.

Unity package and dependency updates:

  • Updated multiple Unity packages in manifest.json and packages-lock.json, including com.unity.ai.navigation, com.unity.collab-proxy, com.unity.ide.visualstudio, com.unity.inputsystem, com.unity.timeline, com.unity.burst, com.unity.collections, com.unity.xr.hands, com.unity.xr.management, and com.unity.xr.openxr to their latest versions for improved features and compatibility. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
  • Updated com.styly.styly-xr-rig package version and adjusted its dependencies' order for consistency.

Project configuration and solution management:

  • Changed the default solution file in .vscode/settings.json from .sln to the new .slnx format and added the corresponding STYLY-NetSync-Unity.slnx solution file, which lists all relevant project files. [1] [2]
  • Updated the Unity editor version in ProjectVersion.txt to 6000.0.70f1 to match the updated package requirements.

Package manager and registry settings:

  • Added com.styly.device-id-provider to the OpenUPM registry scopes in PackageManagerSettings.asset to allow fetching this package from the registry.
  • Updated internal instance IDs in PackageManagerSettings.asset for registry tracking.

@from2001 from2001 merged commit 0b45737 into develop Mar 14, 2026
@from2001 from2001 deleted the upgrade/6000.0.70f1 branch March 14, 2026 08:56
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.

1 participant