co-sic
commented
2 months ago Hey @hartbit thanks for reaching out about this. This was a conscious decision, see this comment for the reasons: https://github.com/gastromatic/calendar-date/pull/303#discussion_r1631458435 . But in hindsight i would not do that again and just stick to the conventions. So sorry for the inconveniences, will not happen again!
Of course this is up to you and your team, but i would strongly encourage to always use pinned versions in your package.json, so something like this cannot happen. Best in combination with e.g. renovate and some sort of ci check in the pipelines.
If you have any other problems with the library or feature requests, let me know :)
edwardmjackson
I just wanted to let you know that version
2.6.0includes backwards incompatible changes and should therefore have required a major version bump to follow semver. For example, in our team, we depend on^2.5.0and a recentnpm installbroke our application becausenpmrightfully downloaded version2.6.0.According to semver's FAQ, one way to fix this issue would be to release a new minor version that restores the renamed functions (without removing the new ones): https://semver.org/#what-do-i-do-if-i-accidentally-release-a-backward-incompatible-change-as-a-minor-version.