The action should not run if no engine files have been modified. If new engine files are being added to the manifest, the version file can be written without having any changes. Installed builds will not run the action due to the path check.
#jira UE-133086
#preflight 61df35b7484d866ec01c8597
#ROBOMERGE-AUTHOR: ben.marsh
#ROBOMERGE-SOURCE: CL 18588751 in //UE5/Release-5.0/... via CL 18588762 via CL 18588785
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Test -> Main) (v899-18417669)
[CL 18588797 by ben marsh in ue5-main branch]
#rb Ben.Marsh
#rnx
#ROBOMERGE-AUTHOR: tim.smith
#ROBOMERGE-SOURCE: CL 18265041 in //UE5/Release-5.0/... via CL 18265047
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
#ROBOMERGE[STARSHIP]: UE5-Main
[CL 18265049 by tim smith in ue5-release-engine-test branch]
RootDirectory, EngineDirectory, UnrealBuildToolPath are now found in BuildUtilities' UnrealBuild namesapce.
The way these are computed has changed. Previously, it was assumed that the application is UnrealBuildTool, and paths were constructed relative to that assembly.
Now, the assumption is that the process is located under a "Engine/Build/DotNET" sub-path and paths are constructed relative to that.
#jira none
#ROBOMERGE-SOURCE: CL 16607440 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v828-16531559)
[CL 16607455 by jonathan adamczewski in ue5-release-engine-test branch]
#rb none
#jira UE-76017
#ROBOMERGE-SOURCE: CL 6916209 in //UE4/Release-4.22/...
#ROBOMERGE-BOT: RELEASE (Release-4.22 -> Main) (v366-6836689)
[CL 6916227 by ben marsh in Main branch]