Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ jwcrypto==1.5.6 ; python_full_version >= "3.9.2" and python_version < "4.0"
pycparser==2.23 ; python_full_version >= "3.9.2" and platform_python_implementation != "PyPy" and python_version < "4.0" and implementation_name != "PyPy"
pydash==8.0.6 ; python_full_version >= "3.9.2" and python_version < "4.0"
pyjwt==2.11.0 ; python_full_version >= "3.9.2" and python_version < "4.0"
python-box==7.3.2 ; python_full_version >= "3.9.2" and python_version < "4.0"
python-box==7.4.1 ; python_full_version >= "3.9.2" and python_version < "4.0"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updating the python-box from version 7.3.2 to 7.4.1 generally is considered to be a good practice because the new version might contain bug fixes or new features. However, how have you ensured that this version bump does not introduce any issues to the existing code that depends on the python-box library? Are there any unit tests or other automated tests that can be run to validate this change?

python-dateutil==2.9.0.post0 ; python_full_version >= "3.9.2" and python_version < "4.0"
pytz==2025.2 ; python_full_version >= "3.9.2" and python_version < "4.0"
pyyaml==6.0.3 ; python_full_version >= "3.9.2" and python_version < "4.0"
Expand Down
Loading