jaeger-2/2.13.0 package update

[octo-sts]

Commit: 63b27e1810a710ac54dc4522da0538e540bdc545

Note: If you need to make manual changes to this PR, apply the skip:staging-update-bot label so the reconciler won't overwrite them.

[octo-sts]

🔢 Build Failed: Dependency Version Mismatch

npm error engine Unsupported engine - Not compatible with your version of node/npm: [email protected]. Required: {"node":">=24"}, Actual: {"node":"v20.19.6","npm":"11.6.4"}

Build Details

Category	Details
Build System	npm
Failure Point	npm install --prefix jaeger-ui/ during jaeger-ui build process

Root Cause Analysis 🔍

The jaeger-ui-monorepo package requires Node.js version 24 or higher, but the build environment is using Node.js v20.19.6. This version incompatibility prevents the npm install from proceeding, causing the entire build to fail.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• jellyfin-web/10.11.0 package update #69450

Suggested Changes

File: jaeger-2.yaml

• modification at line 32 (environment.contents.packages)
  Original:

- nodejs-20

Replacement:

- nodejs-24

Content:

Update Node.js version from 20 to 24 to meet the jaeger-ui-monorepo requirement of Node.js >= 24

Click to expand fix analysis

Analysis

The similar fix shows a pattern of constraining dependency versions when there are compatibility issues. In the jellyfin-web case, the package required npm version between 9.6.4 and 11.0.0, but the build environment had npm 11.6.2. The fix was to add a version constraint "npm<11" in the environment dependencies to ensure a compatible npm version was installed. This same pattern applies to the current jaeger-ui failure - the package requires Node.js >= 24, but the environment is using Node.js v20.19.6.

Click to expand fix explanation

Explanation

The jaeger-ui-monorepo package explicitly requires Node.js version 24 or higher, as indicated by the error message showing 'Required: {"node":">=24"}'. The current build environment is using nodejs-20 package, which provides Node.js v20.19.6, but this doesn't meet the minimum requirement. By changing the dependency from 'nodejs-20' to 'nodejs-24', the build environment will install Node.js version 24, which satisfies the jaeger-ui-monorepo requirement. This follows the same pattern as the jellyfin-web fix where a version constraint was applied to ensure compatibility. The npm version (11.6.4) should remain compatible with Node.js 24, so no npm version constraint is needed.

Click to expand alternative approaches

Alternative Approaches

• Pin to a specific Node.js version like 'nodejs-24.0' if available, though 'nodejs-24' should automatically select the latest 24.x version
• Add a version constraint like 'nodejs>=24' if the package manager supports it, though the Wolfi package naming convention suggests using the major version number
• Check if there's a newer version of jaeger-ui that might have relaxed Node.js requirements, though this would require updating the entire project

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.