Could you consider adopting semantic versioning in this project?
The reason behind this request is that org.webjars:webjars-locator-core is among dependencies managed by Spring Boot's BOM, and with the current versioning scheme (X.Y) Spring Boot's dependency management policy basically considers every release to be a minor, not a patch release. See spring-projects/spring-boot#31560 for some background.
In practice, this means that Spring Boot users will see webjars-locator-core updates only when picking up new minor release of Spring Boot itself. For example, Spring Boot 2.7.0 was released with 0.50 as the managed version of webjars-locator-core and it will stay there for the entire lifecycle of 2.7.x.
Given that this is a very simple library with a single and well defined purpose, I doubt that all of its releases really are to be considered minor releases. 🙂
Additionally, are there any plans for the project to reach 1.x milestone? Milestones page offers no insight into project's roadmap.
Could you consider adopting semantic versioning in this project?
The reason behind this request is that
org.webjars:webjars-locator-coreis among dependencies managed by Spring Boot's BOM, and with the current versioning scheme (X.Y) Spring Boot's dependency management policy basically considers every release to be a minor, not a patch release. See spring-projects/spring-boot#31560 for some background.In practice, this means that Spring Boot users will see
webjars-locator-coreupdates only when picking up new minor release of Spring Boot itself. For example, Spring Boot2.7.0was released with0.50as the managed version ofwebjars-locator-coreand it will stay there for the entire lifecycle of2.7.x.Given that this is a very simple library with a single and well defined purpose, I doubt that all of its releases really are to be considered minor releases. 🙂
Additionally, are there any plans for the project to reach
1.xmilestone? Milestones page offers no insight into project's roadmap.