No release notes

[elyobo]

A major new release has come out, implying breaking changes, but there is no available documentation of what these changes are that I can see. Some docs would be great!

[laug]

This page talks about the 2.0.0 release:
#197

I would also like to know if we can safely upgrade to the new version without needing to make changes to the calling code?
Seems it should be fine if it's just a tooling change though.

[Nefcanto]

It's strange how there is no release in the Releases related to 2.0.1. Does anyone know what that means?

[elyobo]

It means no GitHub release was created even though a new version was published to NPM; they're different systems and don't necessarily need to be kept in sync, but it's common to do so.

[shellscape]

I don't have a lot of confidence that the author is releasing according to semver.

[meduzen-immoweb]

According to the files diff between 1.x and 2.x, there’s at least a difference in Node version support, from 16.14 to 18.17.1. I don’t know if there are any other. Our CI pipeline stays green on this change, but it’s not great.

Let’s hope a changelog comes later.

[Nefcanto]

We also upgraded and our build did not break. Yet we did it blindly, fingers crossed.