Drop engine restrictions#17
Merged
Merged
Conversation
microbit-matt-hillsdon
approved these changes
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The node and npm restrictions were intended for library developers, not for consuming apps.
We explored using
devEnginesto restrict engines for developers instead, but an attempt in a different library resulted in the CI workflow failing. The setup-node step threw a EBADDEVENGINES error (npm version is 11.16 instead of 11.18). The installation of 11.8 should happen after that, but it never reaches there. Instead, we will rely on the consuming apps to ensure we are using the correct engine versions.