Bug Getting errors in new project in unity version 2022.1.21f1

To repro, just create a new urp project in 2022.1.21f1.

Code (CSharp):

1. 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
2.  
3. 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?)

 

Also many errors:

Code (CSharp):

1. Asset Packages/com.unity.shadergraph/Editor/Generation/Targets/BuiltIn/Editor/AssetPostProcessors/ShaderGraphMaterialsUpdater.cs has no meta file, but it's in an immutable folder. The asset will be ignored.

(WebGL target)

 

I'm also seeing errors after updating

Code (CSharp):

1. Library\PackageCache\com.unity.visualeffectgraph@13.1.8\Runtime\Utilities\Playables\VisualEffectActivation\VisualEffectActivationClip.cs(11,12): error CS0246: The type or namespace name 'VisualEffectActivationBehaviour' could not be found (are you missing a using directive or an assembly reference?)
2.  
3. 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
4.  
5. 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?)

Downgrading to 2022.1.20f1 has no errors

 

If it was caught by your devs why was it released?
And why hasn't it been pulled from the release?

 

any hints when 14x will go live out of beta ?

 

Well, if you think you can code the editor better, then... apply for a job and improve it. We, the mortals, will be grateful.

 

I never said I could code the editor better.
Bugs happen all the time, that's why Unity should have official QA testers, as well as automated tests in place to reduce the chances of bugs like this getting released.

And if you do find a showstopper bug like this one is you should fix it ASAP instead of waiting 2 weeks to release a fix.

 

News for out of beta?