You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a maintainer I need to bump the Node.js engine requirements.
Acceptance criteria
Node.js engine bump to 22 for a target date in late April beginning of May
Related GitHub workflows are potentially bumped to include available latest "even version only"Node.js version, like 26
Documentation is updated where applicable
Assumptions and questions
We'll be following a twice a year bump to provide some level of predictability for consumers.
Bumps are targeted for spring and fall, generally April/May and October/November, generally around the times Node.js is rolling in and out support for their LTS versions, schedule
An allowance for security considerations should be made
Typically, a minor or patch version should be released before this type of update since this (removing support) can be considered a breaking change, see chore(release): 1.0.1 #168
As a maintainer I need to bump the
Node.jsengine requirements.Acceptance criteria
Node.jsengine bump to22for a target date in lateAprilbeginning ofMayRelated GitHub workflows are potentially bumped to include available latest "even version only"
Node.jsversion, like26Documentation is updated where applicable
Assumptions and questions
We'll be following a twice a year bump to provide some level of predictability for consumers.
Bumps are targeted for spring and fall, generally April/May and October/November, generally around the times
Node.jsis rolling in and out support for their LTS versions, scheduleAn allowance for security considerations should be made
Typically, a minor or patch version should be released before this type of update since this (removing support) can be considered a breaking change, see chore(release): 1.0.1 #168
Jira Issue: PF-3843