v2.6.0
Properly handle version specifiers
This version greatly improves on the version specifier handling when updating the pyproject.toml
file using either the callable workflow CI - Check pyproject.toml dependencies or the pre-commit hook Update dependencies in pyproject.toml
.
It now utilizes the same logic as is implemented in the pip
package, namely the packaging
Python library to handle the dependencies and requirements listed in the pyproject.toml
file.
To an extent, there is also support for version markers, specifically, specifying a dependency's validity according to a Python language version, e.g., my_package~=1.3; python_version < '3.8'
. However, this support is limited in its scope, and does not support the full reasoning logic otherwise provided by the marker handling in packaging
, meaning for example if you specify different Python language version requirements based on the OS, this may not be respected as intended by the user.
Changelog
v2.6.0 (2023-11-17)
Implemented enhancements:
- Modularize
update_deps.py
further #148
Fixed bugs:
- Ensure version dependency ranges are respected when updating #141
Merged pull requests:
- [Auto-generated] Update dependencies #214 (@TEAM4-0)
- [Auto-generated] Check & update dependencies (
pyproject.toml
) #213 (@TEAM4-0) - [Auto-generated] Check & update dependencies (
pyproject.toml
) #206 (@TEAM4-0) - [Auto-generated] Update dependencies #204 (@TEAM4-0)
- Handle version specifiers #190 (@CasperWA)
* This Changelog was automatically generated by github_changelog_generator