Description
Relax the top end limit of the tomlkit dependency. Python's pip only knows how to handle 1 version of a specific dependency and I am having conflicts within my projects as I require tomlkit>0.11.0 but that is incompatible with python-semantic-release.
Use cases
Currently tomlkit has come out with 0.11.4 as of 13 Aug. To alleviate additional PRs to constantly update and modify the build spec, allow it to update automatically but pin at the lowest minimum requirement. The semver standard should mean you can trust the interface will not break as the minor version updates only new features are added (and of course bugs fixed, which you already imply).
Possible implementation
Ideally, it should be tomlkit ~= 0.10 in setup.py. The ~= is quite effective as it will be equivalent to 0.10.0 <= tomlkit < 1.0.0. Make sure not to add an additional patch number or it changes the effect of ~=.
Related: #337
Description
Relax the top end limit of the
tomlkitdependency. Python'spiponly knows how to handle 1 version of a specific dependency and I am having conflicts within my projects as I requiretomlkit>0.11.0but that is incompatible withpython-semantic-release.Use cases
Currently
tomlkithas come out with 0.11.4 as of 13 Aug. To alleviate additional PRs to constantly update and modify the build spec, allow it to update automatically but pin at the lowest minimum requirement. Thesemverstandard should mean you can trust the interface will not break as the minor version updates only new features are added (and of course bugs fixed, which you already imply).Possible implementation
Ideally, it should be
tomlkit ~= 0.10insetup.py. The~=is quite effective as it will be equivalent to0.10.0 <= tomlkit < 1.0.0. Make sure not to add an additional patch number or it changes the effect of~=.Related: #337