The confusion seems to come from the fact that LTS versions are tagged with the warning. So saying “non-LTS won’t receive updates” it’s not really that helpful.
Am I to assume they’ll patch the version I’m using? It is labeled as LTS after all. If so, great. If not, the LTS tag is about as useful as a chocolate teapot.
In that situation is not a mystery that some people are asking themselves “What’s up with that?”.
3 Likes
A version being LTS refers to the major/minor version. Not the patch version. LTS versions are supported by releasing patched versions. You get fixes by downloading a higher patch version and updating your project to said version. Same as it’s been since 15 or more years ago.
2 Likes
Welcome to the forums! It’s understandable that new Unity users may be confused, especially if they’re not familiar with how LTS versions work or how software update cycles generally operate. Unity LTS versions are typically updated biweekly with new patches at first. As the need for fixes decreases, updates usually move to a monthly schedule.
For example, the current 6.3 LTS release is version 6.3.9. That means it has already received nine updates since its public release, and it will continue to receive more. That’s the purpose of an LTS release: ongoing updates that provide fixes and improvements.
LTS versions marked with a warning are older builds. The warning exists to indicate that you should update. Asking when to update is somewhat unusual, since the warning does not appear on the latest patched version. A good practice, especially for new Unity users, is to check Unity Hub regularly for available updates. Updates are released frequently and can be easy to miss if you’re not yet familiar with the ecosystem.
It actually is, because once you understand what LTS versions are and that patched versions have already been released, there isn’t much room for confusion. There was a bug, and it has been fixed in the versions that are still supported. Nothing mysterious about that. That said, for new users of Unity or software tools in general, the confusion as I mentioned is understandable.
Re-reading the thread, I see I might’ve gotten ahead of myself a little bit. At first I thought I had to do a full version upgrade. That’s why I addressed the explanation about non-LTS vs LTS. My bad.
This clears it up for me, though. Thank you!
Yeah, exactly. That’s what I meant by “not a mystery”. Maybe I was a tad dramatic?
Anyway, thanks for the breadth of information.
3 Likes
As mentioned on some other threads, wiping the package cache can fix this temporarily (until a package is changed). This could be helpful if you need to stay on an old editor version.
mac ~/Library/Caches/Unity/upm
win %USER_DIR%\AppData\Local\Unity\cache\upm
And just btw, I do feel like Unity’s own messaging has created some confusion here. There was a lot of fanfare about Update releases being “production-ready and fully supported” and I think this may have mislead some newer developers. See here: Unity 6.1: Supported Update with Enhanced Performance | Unity
1 Like
The link you provided shows an image where support for version 6.1 ends when 6.2 is released, and support for 6.2 ends when 6.3 is released. In contrast, versions 6.0 and 6.3 in the image show support windows that extend beyond the release of the next version. I don’t see how anyone could be confused and expect support for versions 6.1 and 6.2 after 6.3 has been released based on this image:
I mean, it’s even titled “Unity 6 Release Support”
1 Like
The SDKs I use also rely on APIs removed in version 6000.3, so I cannot upgrade. I agree with @XylaTV s opinion. Furthermore, If Unity cannot provide builds because it’s not LTS, they should at least offer a way to disable warnings in the Unity Hub.
I find the response mentioning “RTFM” to be rude.
3 Likes
You shouldn’t have upgraded. If anything, you should have stayed on the latest LTS version that actually supports the APIs you need, Unity 6.0. That’s what most studios do, they use the latest LTS version for projects in production.
Sure, “RTFM” sounds rude to people who don’t read documentation. But what’s even more rude is pretending none of this is their responsibility and fill the forum with posts about it. Unity uses the same versioning system the rest of the software world uses. It clearly labels LTS releases. The Hub literally marks the recommended version with the LTS tag and a “recommended version” message. There’s even a color-coded support window chart spelling out which versions are supported and which are not, which I posted above. At some point, claiming ignorance stops being an excuse.
Yet people still show up on the forums insisting it’s Unity’s fault they chose to run a version that doesn’t receive updates anymore. That’s not a tooling problem, that’s a decision-making problem.
So yes, “RTFM” might sting. But it’s good advice. In the long run, people learning to read the documentation of the software they use, will save them far more pain than blaming everyone else for choices they made.
3 Likes
Sorry, I’m very new to unity. How do I download the new version?
The same way you download the one you have
1 Like
Heh. Both Unity installs I have - one says ‘
WARNING’ and the other says ‘ Security Alert’. D’oh!
Tell us which Unity version you have
Over the past 20 years in this field, I haven’t done anything particularly extraordinary, but I’ve created quite a few products, made small contributions to open-source projects, and collaborated with various people.
Not every project develops under ideal circumstances.
For example, the project mentioned here was developed on 6000.2 and we were planning to upgrade to 6000.3. However, we couldn’t upgrade due to one small module we were using, and modifying that module was far down on our priority list. It was working, after all.
However, when Unity Hub updated, a warning flag appeared. If this issue had been like a previous vulnerability requiring an immediate engine update, we would have done it.
So, I proposed an alternative: adding a feature to disable the warning.
But bringing up LTS again and mentioning “RTFM” there comes across as hostile, as noted in the wiki.
We come to the forums to solve problems, not to be scolded.
As mentioned earlier, please understand that not all projects develop under ideal conditions. I hope we can exchange opinions to solve problems, not just resort to “RTFM.”
2 Likes
In the end, what happened may actually be a good thing. After 20 years, it might finally reinforce the realization that production projects should use only LTS versions. This is just an annoying notification and a minor inconvenience not a breaking bug that makes Unity unusable. Of course, it could have been a breaking bug, and that is precisely why this outcome might be beneficial, if people take responsibility for their choice.
Projects are rarely developed under ideal conditions, as you mentioned. For that reason, it is the programmer’s responsibility to control what they can and to be accountable for those decisions, rather than shifting responsibility to someone else.
My position has been clear from the beginning: using Unity 6.2 and not an LTS version for a project in production was a bad decision. At the very least, it can serve as a valuable lesson for the future, if people acknowledge that they are responsible for not understanding the support window.
If they continue to believe that Unity is responsible, they are likely to repeat the same mistake again and again, even over the next 20 years. Real change only happens when someone recognizes that the mistake was their own and makes a conscious effort not to repeat it.
Unity is not responsible in this case because all information regarding the support window is clearly documented in many sources. Therefore, complaints about the support window are misplaced, since the information was available and should have been reviewed beforehand.
So my opinion is that reading the manual prevents many problems and avoids the unnecessary drama that arises when people choose not to read it or simply ignore it, as seems to be the case here. If you consider “RTFM” to be hostile, I will put it more plainly:
Read the manual and do not ignore it.
I do not believe there is anything rude or hostile about saying that, on the contrary it is good advice.
2 Likes
I don’t get it… How i do it?
Mine is on 6.3 and 6.0 
An amazing first post from a developer with 10 years of experience in Unity. The fact that you never needed to use the forums for a decade but had to now because of a non-breaking warning is extraordinary.
3 Likes
Please follow this video
Unity Package Manager Invalid Signatures FIX (2026) | Invalid Packages Error Solved
please check this. I hope this will help you.