It depend if you are using them in custom packages as references or dependencies. If the data changed in places where people had to once type out the package name, a folder location, and ect it can break some code or dev made packages.
Which is a problem because Unity recently had a long problem of wrong named package references crashing any project that you tried to open before making it to the first scene in editor.
fair enough, i know that sometimes you cant go back versions cos whatever isnt available and then you cant remove what isnt there… and it can get messy, so im not overly surprised, but ive not referenced package areas directly so, i was curious why it was an issue… thanks for explaining
Basically the majority of packages in the asset store that work across SRPs have to know which SRP they are running under, and often need a define to write code specifically for each one since much of the code is not shared. Strangely, Unity doesn’t provide this functionality, so either people are looking up these packages by name/path, or using an asmdef which references the package and sets the define. If Unity changes this stuff around, they’ll likely break an ungodly amount fo external assets and projects.