This cookbook repo falsely claims that it adheres to Rubygems Semantic Versioning Policy (https://github.com/Foodcritic/foodcritic#changelog). When brought to the attention of the cookbook repo maintainers, it is brushed off and ignored. An example is in the release of 12.3.0 where existing functionality was removed that broke existing functionality due to improper versioning of the new release was made: https://github.com/Foodcritic/foodcritic/issues/726#issuecomment-363663092. Semantic versioning policy does state that removal of a feature like this requires that the version be bumped by the major version, as a breaking change.
Rather than accepting the mistake and re-releasing as a breaking change, the maintainers stand by a false stance of "best effort" means they can do whatever their whims are today.
This
cookbookrepo falsely claims that it adheres to Rubygems Semantic Versioning Policy (https://github.com/Foodcritic/foodcritic#changelog). When brought to the attention of thecookbookrepo maintainers, it is brushed off and ignored. An example is in the release of 12.3.0 where existing functionality was removed that broke existing functionality due to improper versioning of the new release was made: https://github.com/Foodcritic/foodcritic/issues/726#issuecomment-363663092. Semantic versioning policy does state that removal of a feature like this requires that the version be bumped by the major version, as a breaking change.Rather than accepting the mistake and re-releasing as a breaking change, the maintainers stand by a false stance of "best effort" means they can do whatever their whims are today.