Version 4.0.1 published to NPM as 3.0.2

[brennan-wright]

It looks like the new version of the Brevo node package 4.0.1 was published to NPM as both the 4.0.1 version as well as the 3.0.2 version, breaking semver

If I understand this correctly, I believe the 3.0.2 version should be unpublished or deprecated from NPM. Not sure if this is possible due to restrictions with the NPM registry though.

[mourraille]

Thanks for the report, we are looking into it.

[mourraille]

Thanks for pointing this out.

3.0.2 was not an official release. The latest supported version in the 3.x line is 3.0.1:
https://github.com/getbrevo/brevo-node/releases/tag/v3.0.1

Version 3.0.2 was briefly published during the testing phase of the 4.0 release and wasn’t intended as a public semver release. Because of npm policies, it can’t be removed, but we’re marking it as deprecated/broken to avoid confusion.

For production use, please use 3.0.1 or >=4.0.1.

[konradliebig]

You could maybe also republish 3.0.1 as 3.0.3 to make sure that all users that accidentally already installed 3.0.2 get an update to a working version again.

[mourraille]

Absolutely. We will publish a copy of 3.0.1 as 3.0.3 briefly