[Resolved: Please update affected versions of Unity]
On the 23rd of January 2026 we detected a false error where the Package Manager was incorrectly marking Packages as invalid. This issue has since been resolved but you will need to update your Editor version to the next available one. To help identify which builds have the issue, we will soon implement a warning badge in the Hub which will look something like this;
As a reference, below are the affected versions and which versions are ideal to upgrade to. If the version is listed here and you don’t see the new warning, or see a different warning, please still upgrade to the next fixed version.
Affected 6000.0 versions: update to 6000.0.66f2 or later:
6000.0.55f1
6000.0.56f1
6000.0.57f1
6000.0.58f1
6000.0.58f2
6000.0.59f2
6000.0.60f1
6000.0.61f1
6000.0.62f1
6000.0.63f1
6000.0.64f1
6000.0.65f1
6000.0.66f1
Affected 6000.2 and 6000.3 versions: update to 6000.3.5f2or later:
Would it be possible to release a new 6000.2 build with this issue fixed? My project can’t be upgraded to 6000.3 because of a plugin not supported anymore.
serisously f### off i just upgraded my entire project to next new version because of this security error that you had. And now my upgraded project has this warning thing on and i need to upgrade again. I have completely lost any trust in this software.
Great messaging guys.
Hey we have a false error here. We wont go into any details but to get rid of error upgrade your ENTIRE PROJECT AGAIN. Give us at least info is this purely cosmetic or not? will we run into problems if we continue with current version. I wont uprade again. You are bankrupting my entire dev process.
I would like to know this also. My current project is just a proof of concept so unless something is going to fatally break I’m happy to stay where I am.
If you continue using the version with the warning, you might face issues like packages showing as Invalid, Package Manager errors, or even build problems. The biggest risk is that it can waste your time in the future. If you get any random error, you might think it’s your code mistake and spend hours trying to fix it, but actually the problem could be from the editor version itself. Since this was an issue from Unity, it’s safer to update to the next available version and avoid unnecessary confusion.
Updating now can save you a lot of debugging time later.
6.2 is and was a short term support version, it will only receive critical security updates, it was clear from the start and BTW that warning is not something that will break your project, is just a warning.
The recommendation to update our projects every time Unity version 6.2/3/allOfThemEventually just shifts the responsibility to deal with the issue from your software to our projects. If we update, we’ll have new, unnecessary confusion to deal with. Please take the time to patch the issue so that your product works as intended.
Unity’s versioning system is clear. The only versions suitable for production are the LTS releases, which provide long-term support. Versions 6.1 and 6.2 are not LTS, they are technical releases that include new features after beta but do not offer long-term support.
Any project intended for production rather than as a hobby, should use an LTS version. Expecting non-LTS versions to receive ongoing bug fixes reflects a misunderstanding of how Unity’s versioning works. That responsibility falls on the project lead, not Unity.
Complaining about a system that has been in place for years, as if it were Unity’s fault, reflects a common and irresponsible pattern in the forums whether the issue is a lack of version control for a lost project, logical errors in code for a bug, or misunderstandings about LTS support: “It’s not my fault, it’s someone else’s”.
RTFM will still be relevant even when the manual is downloaded directly into our brains They’ve been doing Tech vs LTS since what, 2017? So a decade almost. But folks still get caught out…
Is it a Store/Asset plugin? “Unsupported” for assets can just mean the creator doesn’t have time for full support - but if they’re still active, they might do a “pity patch”. Otherwise, If the code is editable, you could try posting on the forums for that asset (or under the Store “tag”) and if the creator isn’t able to patch it, a fellow user might be able to help.
Folks, it’s just a warning - you might have build/package errors, but they don’t say it’s fatal, or anything security-related. Seems like it’s okay to ignore until/unless it causes you issues.
am i mising something? i have always downloaded from official releases tab and they were labeled as LTS. Now they are not lts versions? i am so confused
Unity patches supported versions regularly. You’re just on earlier patch versions of 6.0 and 6.3. You just have to download the latest patch version and update your projects.
Patch versions are released every few weeks. Updating your project to the latest patch version when needed is a very common thing to do.
LTS means they get supported with patches long term. I’m not sure what you seem to think it means.
Let me clarify, because I realize that not everyone who uses Unity comes from a technical background, many are artists and may not be familiar with how software versioning works.
In most software projects:
Alpha versions are early builds where features and APIs are not yet finalized. Changes are expected, and functionality may be incomplete.
Beta versions have a finalized feature set. They are released so users can report bugs while the company focuses on stabilization.
Technical release and LTS (Long-Term Support) releases may both contain bugs, but they differ in support policy.
An LTS version receives updates and bug fixes for an extended period, even after newer versions are released. A technical release stops receiving updates once the next major version becomes available.
For example, versions 6.0 and 6.3 will continue receiving patches and fixes during their support window. Versions 6.1 and 6.2 will not. That difference is what caused you confusion in your screenshot: the warning appears because those versions require patching to a supported release. Non-LTS versions do not receive ongoing patches and that’s why they shouldn’t be used for production.
This is why I said the responsibility lies with whoever is the project lead or acting in that role. They are expected to understand these distinctions. Unity clearly identifies which versions are LTS, just like other software vendors do. The installer includes an LTS label, and it also has a message with the recommended version when users browse available installations.
What else can Unity do? Have a magic hand reach out of the monitor and start slapping whoever tries to install a non-LTS version for a production project? At some point, responsibility falls on the user. Yet there will still be people who insist: "It’s not my fault, it’s someone else’s, it’s Unity’s fault", because in their minds they never are the ones responsible.
They’ve been doing Tech vs LTS since what, 2017? So a decade almost. But folks still get caught out…
