Now Available: Unity Hub 3.17.3

Unity Engine
, ,
1

The Unity Hub team is rolling out the latest 3.17.3, and we are officially introducing native support for GitHub and GitLab directly within the Hub! This is a major step toward making your source control workflow seamless from the very start of a project. With this update, you can:

  • Create new projects connected to a GitHub or GitLab repository during the initial creation flow.
  • Add existing GitHub or GitLab repositories directly to the Hub.
  • Connect a project you’ve already started to a new GitHub or GitLab repository.

Additionally, this release also introduces native support for Windows ARM64, ensuring a more performant experience on Arm-based devices.

We want to hear about your experience:

  • Do these new features help bridge a gap in your existing source control workflow?
  • What other source control-related features in the Hub would make your life easier?

Please share your thoughts, questions, or any issues you run into in the comments below. We’re looking forward to hearing what you think!

see release notes

What’s New in 3.17.1

April 14, 2026

  • Native GitHub and GitLab integration
  • In the New Project flow, GitHub and GitLab are now available as source control providers, and when selected a new GitHub/GitLab repository will be created.
  • In the Projects list options for a project, Use Unity Version Control has been renamed to Use source control, and existing projects can be connected to new GitHub or GitLab repositories.
  • The following features are available when creating a new project or connecting an existing project:
  • A dismissible warning message is shown if Git LFS is not installed, with instructions on how to install.
  • Additional repository configurations such as: visibility level (public or private), namespace/owner, repository description, and default branch name are available in the “Additional Configurations” expandable menu
  • For projects using Unity Editor version 6.3+, users can optionally create and push their first commit to the repository
  • A .gitignore will be added to new GitHub/GitLab projects
  • If Git-LFS is installed, users can optionally create their projects with a .gitattributes file and LFS support pre-enabled in the repository
  • The project will have git initiated and the remote origin set to the newly created repository
  • In Projects > Add from repository, repositories from GitHub and GitLab can be added to the Hub, in addition to Unity Version Control (UVCS) repositories.
  • Authentication for GitHub and GitLab is done via Personal Access Tokens (PAT)
  • A button to generate a PAT with the required scopes is available in the Authentication flow
  • For GitLab the scopes required are “api, read_user” and for GitHub classic tokens the scope required is “repo”. GitHub fine-grained tokens are also supported, and need to be created with both the Administration and Contents permissions, set to “Read and write”
  • PATs are cleared by default when signing out of Unity Hub. This option can be disabled in the settings tab.
  • PATs are stored securely on the user’s local machine.
  • Settings > Security & Privacy has been updated to include source control settings
  • A Source Control section has been added where users can connect to or disconnect from GitHub and GitLab.
  • A Local Storage section has been added where users can configure whether or not the Hub should clear Personal Access Tokens from device storage upon signing out of the Hub.

Projects

  • Project rows expanded details for projects connected to source control now show the current branch and remote repository size.
  • Project source control column shows the icon of either GitHub, GitLab, or UVCS, depending on source control provider and hovering over the icon will display an external link to that repository
  • Upon new project creation, this column will be populated once the Editor has opened.
  • When clicking on the Editor column of a project, the last opened platform will now be shown instead of Current platform. If the project has not yet been opened, Current platform will be displayed.
  • Projects > Add from repository flow has been updated
  • Adding from repository is now done in a single step
  • The flow has been decoupled from the Editor.
  • A project can be added with a missing Editor version, which the user can manage at a later time.
  • The Editor will no longer open once the project is added.
  • A branch or changeset/commit selector has been added for all source control providers
  • Multiple copies of the same repository can be added to the Hub
  • The cloning process of repositories is now executed as a background task, visible via the new background task menu in the top bar.

Installs

  • A confirmation dialog now appears when you choose to uninstall an editor. This can be permanently turned off in Settings > Installs.

General

  • Hub is now natively available for Windows ARM64.

Bug fixes & improvements

  • The “Send Feedback” option in the profile menu has been replaced with a link to the Unity Hub Forums.
  • In the top bar, the documentation button now shows a menu with links to both the Hub documentation and Unity Editor documentation.
  • Fixed an issue where the CLI would download the incorrect Editor architecture on ARM Windows.
  • Fixed the CLI help text not displaying correctly.
  • Fixed an issue on the New project page where switching Editor versions would sometimes reset inputs such as project name and location.
  • Fixed an issue where the incorrect UVCS server location was displayed.
  • Improved Editor installation speed on Windows.
  • Improved file monitoring performance for tracking project changes.
  • Updated security-related dependencies to address known vulnerabilities.

Edit: Added patch version release notes:

What’s New in 3.17.2

April 17, 2026

Bug fixes & improvements

  • Fixed an issue where users experienced high CPU usage during startup caused by excessive file watching and missing version control configurations.
  • Fixed an issue on Linux where .deb package installation could fail on some setups when AppArmor profile loading could not complete in the kernel.
  • Fixed an issue where the bundled Unity Version Control install or the cm on PATH could become broken, leaving version control in an unusable state.

What’s New in 3.17.3

April 21, 2026

Bug fixes & improvements

  • Fixed high ambient CPU usage for users with projects connected to version control.
12 Likes
Now Available: Unity Hub 3.17 beta
April - In Case You Missed It
2

OMG this is great, thank you

2 Likes
3

It was available since March in the beta channel :slightly_smiling_face:

4

yeah I gave up on the beta versions after it got crappy with me, so im back on production builds, so yes, happy days

5

you guys are on fire with the hub updates! :fire: :exploding_head:

1 Like
6

Thank you for these updates, this is what we need as developers.

BTW, just don’t deprecate Unity version control, I love working with it. :sweat_smile:

1 Like
7

BREAKING:

After updating, it renamed my project “Build Profile” to “BuildProfile”, causing my active Unity editor to freeze and go strange with machine code in logs → then killed my editor scripts pointing to build profile, and likely killed my CI/CD as well that used this.

…why would this even cause breaking changes to the actual editor? I’m using a LTS just to avoid this kind of mess :frowning:

EDIT: It’s actually worse than I thought - Build Profile in Unity will say you’re on your {last buiild profile} as active, but you’re not actually. This is going to cause a mess.

1 Like
8

Just updated HUB
Now I see part of my project as connected to git but only part of them

HUB dont see all connection for some reason, may be it tool only into current project folder and dont travel up hierarchy.

While git source control is half done it is definitely step in right direction, Thanks :slight_smile:

9

Extremely high CPU usage after this update. CPU load constantly spikes to 30-40%. Tried turning off real-time protection - nothing changed. About 10 projects in the hub. Windows 11. Got this right after the update.

image
image959×208 13.4 KB

7 Likes
10

Any projects on unplugged external drive?

11

I guess there is problem with this version 3.17.1 windows 11, how can I downgrade it with older version like 3.16.x, I can’t find the older versions

12

Everything seems normal to me.

13

Same problem with @Demian why did you hide older versions for unityhub I don’t understand

2 Likes
14

Hi @zafery @Demian @unity_EC22A254A041D152C1BE

We’re looking into the issues you reported. If this is a is a blocker, please download a deprecated version from our Docs page: Install a deprecated Hub version • Unity Hub • Unity Docs

Thank you for your patience while we investigate!

3 Likes
15

@Demian, @BattleAngelAlita, @zafery, we are actively investigating this issue.

would you also be able to file a bug ticket in the Hub? This would really help us in diagnosing and fixing this issue.

1 Like
16

I’m tired of seeing updates in a project especially the ones from Unity packages that usually are compatible with that editor project version and yet I’ve got to load the project, wait compile, go through and click update and wait compile, wait compile for every damn update.

When this hub thing exists that could have some way to manage the package.json of a project a lot better and easier and let users specify which packages they want to upgrade, manage external packages added to it (Hell even better provide an options to disable packages without removing them completely so they can be re-enabled for the project outside of the editor before loading them etc etc.. then load the project and wait for compile one time instead of multiple recompiles to do updates… hopefully to find no errors but still the time saved would better..

Sometimes I just copy parts of package.json contents over from one active project to next when they are the same Unity version or I already know the packages work fine, save myself this nonsense waiting for recompiles per update. Why hasn’t anything been done about this already?! I didn’t ask for new project to default to cloud storage either, didn’t ask for git integration just use a client.

Still can’t even duplicate a project with a new project name defined for making test repo’s, just another area the hub fails to make things just a little easier. Not asking for a proper export project tool that only exports what is actually used in scenes like the build output so test repo’s can atleast be started off without gigabytes of assets like trees that aren’t even used scenes etc.

17

I’m seeing an issue where clicking on a project has no immediate visual response. I can still navigate and interact with Hub and it visually responds, but there is no indication that a project is immediately opening.

In fact, I don’t believe that it is. After 30 - 45 seconds, the editor splash screen finally appears and begins the project boot sequence. At that point, things continue as normal.

Is there a log I could look at or share with the team to find out what is happening during that delay? I don’t believe this is related to any of the VCS changes in the Hub with this version as it’s happening with both plastic and git based projects.

18

Hi @Andrew-Carvalho, can you please file a bug ticket by following the steps here.

this will include the logs in your request and allow us to debug the issue you are seeing.

19

Will privately hosted GitLab instances be detected sometime in the future?

1 Like
20

Yes! @Etonix, we had several user’s request this feature on the forums, so we have added it to our roadmap! It will be coming soon :slight_smile:

1 Like