Skip to content

ci: Fail-fast "npm ci" if deps require unsupported node version#1172

Merged
maxreichmann merged 5 commits intomainfrom
ci-node-engine-strict
Oct 28, 2025
Merged

ci: Fail-fast "npm ci" if deps require unsupported node version#1172
maxreichmann merged 5 commits intomainfrom
ci-node-engine-strict

Conversation

@maxreichmann
Copy link
Copy Markdown
Member

@maxreichmann maxreichmann commented Oct 27, 2025

+ ci(package.json): Update node version to current LTS (22) + latest (24)
+ ci(github-ci.yml): Update node version to current LTS (22)
+ ci(test.yml): Remove node20 for test matrix


When upgrading a dependency to a newer version, it might require a different node version than before which could be unsupported by the repo. Unfortunately, this could be easily overseen.

This PR adds the flag --engine-strict to the dependency installation step during the GH Actions job. Incase such a version requirement change, this flag will now fail-fast the job which should attract attention.

@maxreichmann maxreichmann requested review from a team and removed request for a team October 27, 2025 10:19
@maxreichmann maxreichmann force-pushed the ci-node-engine-strict branch 2 times, most recently from ba38125 to 142829c Compare October 27, 2025 13:47
@maxreichmann maxreichmann force-pushed the ci-node-engine-strict branch from 142829c to 8bf5b5a Compare October 27, 2025 13:48
@maxreichmann maxreichmann requested a review from a team October 27, 2025 13:54
Copy link
Copy Markdown
Member

@matz3 matz3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The individual package.json files (within the packages folder) should also be aligned with this change.

@maxreichmann
Copy link
Copy Markdown
Member Author

maxreichmann commented Oct 28, 2025

@UI5/ui5-team-cor-fnd
Currently, the tests in the matrix with Node20 fail because Execa detects the unsupported version. If we want to bump our node version requirements, we have to adjust the versions in the matrix too (even though we aren't even using --engine-strict here). Or do you have other ideas / opinions?

RandomByte
RandomByte previously approved these changes Oct 28, 2025
@maxreichmann maxreichmann merged commit 935b292 into main Oct 28, 2025
14 checks passed
@maxreichmann maxreichmann deleted the ci-node-engine-strict branch October 28, 2025 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants