A microservice of mine was specifying version ^2.2.1 of this repo in its package.json which indicates that it should pull any version below 3.0.0. The service had not been deployed since early January and it broke on npm install during a recent redeployment. This appears to be due to the fact that v2.6.0 is not backwards compatible with Hapi prior to v10.0.0. Breaking changes should increment the major version so I believe the current release should be correctly titled v3.0.0.
A microservice of mine was specifying version
^2.2.1
of this repo in its package.json which indicates that it should pull any version below3.0.0
. The service had not been deployed since early January and it broke onnpm install
during a recent redeployment. This appears to be due to the fact thatv2.6.0
is not backwards compatible with Hapi prior tov10.0.0
. Breaking changes should increment the major version so I believe the current release should be correctly titledv3.0.0
.