Bug 2022.1.21f1 Doesn't work with URP?!

Booted up a project that was from 2022.1.20f1 today using 2022.1.21f1 and found that I get this unclearable error. It even happens in empty projects that just use URP + Shadergraph at the recommended versions. How does very simple stuff like this get past QA?!

Library\PackageCache\com.unity.shadergraph@13.1.8\Editor\Generation\Targets\BuiltIn\Editor\ShaderGraph\Targets\BuiltInSubTarget.cs(33,28): error CS0246: The type or namespace name 'BuiltInShaderGraphSaveContext

 

The same here. Works on macOS, but fails on Windows.

Library\PackageCache\com.unity.shadergraph@13.1.8\Editor\Generation\Targets\BuiltIn\Editor\ShaderGUI\BaseShaderGUI.cs(212,34): error CS0103: The name 'MaterialAccess' does not exist in the current context

Library\PackageCache\com.unity.shadergraph@13.1.8\Editor\Generation\Targets\BuiltIn\Editor\ShaderGraph\Targets\BuiltInSubTarget.cs(33,28): error CS0246: The type or namespace name 'BuiltInShaderGraphSaveContext' could not be found (are you missing a using directive or an assembly reference?)

 

Same here !

Edit:
Downgraded to 2022.1.20f1 it works now.

 

I also have errors with packages in Unity 2021.2.21 and HDRP.
Unity 2021.2.21 is the worst build in the last year

 

Same here.

 

Great engine stability right us developers constantly feeling burned by this. I should learn to not try brand new releases so soon but they do go through QA. More an issue of the package manager it feels at times but URP is basically the de-facto render pipeline to start with so it should just *work*

 

Same problem.

 

Also got me. Going to try 2022.1.20f1, now...

 

Same with empty hdrp project.

 

Also encountered the same error on Unity 2022.1.21f1 with the build target: Android

 

same here, exact same issue... had to spend a lot of time downgrading...

 

2022.1.22 just released. Not seeing this issue mentioned in the changelogs, but downloading now to check it out. https://unity3d.com/unity/whats-new/2022.1.22

Edit: So far so good, not seeing the error in 2022.1.22.

 

Did it fix the issue?

 

It looks like it did. Not seeing the error anymore after upgrading.

 

Updating from 2022.1.20 to 2022.1.22 works for me without errors