Skip to content

Conversation

@onesignal-deploy
Copy link
Collaborator

@onesignal-deploy onesignal-deploy commented Mar 24, 2025

Changes

@fadi-george fadi-george requested a review from sherwinski March 24, 2025 21:35
@sherwinski
Copy link
Contributor

🎉 This PR is included in version 3.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Comment on lines -24 to +28
"node": ">=8",
"npm": ">=5"
"node": ">=22",
"npm": ">=10"
Copy link

@tkhquang tkhquang Mar 27, 2025

Choose a reason for hiding this comment

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

Hi @fadi-george @sherwinski , any reason for this sudden change? This version is not flagged as breaking change but this alone causes a lot of trouble when upgrading, for example, from 3.0 to 3.2

[2/4] 🚚  Fetching packages...
error react-onesignal@3.2.0: The engine "node" is incompatible with this module. Expected version ">=22". Got "20.17.0"

Node 20 is still in maintenance and it should be supported

Copy link
Collaborator

@fadi-george fadi-george Mar 27, 2025

Choose a reason for hiding this comment

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

@tkhquang Sorry for that, will push a change to lower the range to 14.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hey @tkhquang, thanks for pointing that out. Agreed that the range shouldn't be bumped so aggressively - we'll patch a fix for it soon.

Copy link
Collaborator

Choose a reason for hiding this comment

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

3.2.1 a fix to the node engines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants