YARN-11902.Fix build failure caused by mktemp@2.0.2

[dilrajsourabh]

Description of PR

JIRA: YARN-11902. Fix Hadoop Yarn UI build failure caused by mktemp@2.0.2.

A build failure occurs in the Yarn UI module during dependency installation due to an incompatible version of mktemp@2.0.2, which enforces a Node.js engine requirement of 20 || 22 || 24.
The current Hadoop build environment uses Node.js 12.22.1, resulting in the following error:

error mktemp@2.0.2: The engine "node" is incompatible with this module. Expected version "20 || 22 || 24". Got "12.22.1" error Found incompatible module.

• Root Cause
  The mktemp package was pulled in as a transitive dependency.
  Version 2.x introduced a strict Node.js engine requirement (≥20), which is incompatible with the current Node 12 environment.

• Fix
  Pinned the mktemp dependency to a compatible version (0.4.0) using Yarn's resolutions block in package.json:
  "resolutions": { "mktemp": "0.4.0" }
  This resolves the build failure without requiring a Node.js upgrade.

How was this patch tested?

ci

For code changes:

• Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
• Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

[hadoop-yetus]

💔 -1 overall

Vote	Subsystem	Runtime	Logfile	Comment
+0 🆗	reexec	15m 24s		Docker mode activated.
			_ Prechecks _
+1 💚	dupname	0m 0s		No case conflicting files found.
+0 🆗	codespell	0m 0s		codespell was not available.
+0 🆗	detsecrets	0m 0s		detect-secrets was not available.
+0 🆗	jsonlint	0m 0s		jsonlint was not available.
+1 💚	@author	0m 0s		The patch does not contain any @author tags.
			_ trunk Compile Tests _
+1 💚	mvninstall	34m 23s		trunk passed
+1 💚	shadedclient	60m 14s		branch has no errors when building and testing our client artifacts.
			_ Patch Compile Tests _
+1 💚	mvninstall	0m 16s		the patch passed
+1 💚	blanks	0m 0s		The patch has no blanks issues.
+1 💚	shadedclient	24m 59s		patch has no errors when building and testing our client artifacts.
			_ Other Tests _
-1 ❌	asflicense	0m 36s	/results-asflicense.txt	The patch generated 1 ASF License warnings.
		103m 48s

Subsystem	Report/Notes
Docker	ClientAPI=1.52 ServerAPI=1.52 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8108/1/artifact/out/Dockerfile
GITHUB PR	#8108
Optional Tests	dupname asflicense shadedclient codespell detsecrets jsonlint
uname	Linux 005f2d135106 5.15.0-156-generic #166-Ubuntu SMP Sat Aug 9 00:02:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Build tool	maven
Personality	dev-support/bin/hadoop.sh
git revision	trunk / 94bbfb4
Max. process+thread count	634 (vs. ulimit of 5500)
modules	C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui
Console output	https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8108/1/console
versions	git=2.25.1 maven=3.9.11
Powered by	Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

[ayushtkn]

LGTM

Can u assign the jira ticket on your name or drop a comment on the jira with your id, so we can assign the ticket and attribute the contribution to you

[dilrajsourabh]

LGTM

Can u assign the jira ticket on your name or drop a comment on the jira with your id, so we can assign the ticket and attribute the contribution to you

Just adding a quick follow-up — since my ASF Jira account setup is still underway, I’m not yet able to self-assign or comment directly on the Jira issue. When convenient, could you please proceed with merging this change? I appreciate your assistance.
@slfan1989 @ayushtkn thanks!

[Sourabh-Dilraj]

LGTM
Can u assign the jira ticket on your name or drop a comment on the jira with your id, so we can assign the ticket and attribute the contribution to you

Just adding a quick follow-up — since my ASF Jira account setup is still underway, I’m not yet able to self-assign or comment directly on the Jira issue. When convenient, could you please proceed with merging this change? I appreciate your assistance. @slfan1989 @ayushtkn thanks!

Just a quick follow-up — my ASF Jira account setup is still in progress, so I’m unable to self-assign or comment directly on the Jira issue at the moment.

When you get a chance, could you please go ahead and merge this change?

Thanks for your help! @slfan1989 @ayushtkn

[slfan1989]

@dilrajsourabh Thanks for the contribution! Merged into trunk.

[steveloughran]

do we need this in 3.4.x?

[Sourabh-Dilraj]

do we need this in 3.4.x?

Yes. I think we need to add this in 3.4.x line as well.