Open TheTrueWhiteOwl opened 4 months ago
This would also reduce the impacts and the necessity of having this issue (https://github.com/hrsh7th/nvim-cmp/issues/231) for documenting the breaking changes. These would already be clearly indicated by a change in the major version. (e.g. going from v1.x.x
to v2.0.0
).
Duplicate of https://github.com/hrsh7th/nvim-cmp/issues/1719
When will
nvim-cmp
get its next release?The last and only one (
v.0.1.0
) was in August 2022, almost two yeas ago...Hasn't the functionality and the public API of this plugin mostly been defined by now, and hence this plugin should probably already be at major version:
1
(i.e.v1.0.0
)?I believe it would be beneficial if
nvim-cmp
would start including releases, following(semver)
[https://semver.org/] such that users can guarantee that their nvim config does not break when backwards incompatible API changes are made. As an example take alazy.nvim
user: