build(deps-dev): bump deptry from 0.14.0 to 0.16.1

[dependabot]

Bumps deptry from 0.14.0 to 0.16.1.

Release notes

Sourced from deptry's releases.

0.16.1

What's Changed

Bug Fixes

• Skip type checking blocks whether future annotations are used or not (#662)

Full Changelog: fpgmaas/deptry@0.16.0...0.16.1

0.16.0

What's Changed

Breaking changes

typing.TYPE_CHECKING handling

Imports guarded by typing.TYPE_CHECKING when using from __future__ import annotations are now skipped. For instance:

from __future__ import annotations
from typing import TYPE_CHECKING
if TYPE_CHECKING:
# This import will not be extracted as it is guarded by TYPE_CHECKING and from __future__ import annotations
# is used. This means the import should only be evaluated by type checkers, and should not be evaluated during runtime.
import mypy_boto3_s3

See https://deptry.com/usage/#imports-extraction for more information.

requirements.in handling

On projects using pip requirements format for defining dependencies, if requirements_files option is not overridden, deptry will first search for a requirements.in file before requirements.txt, to better support projects using pip-tools and the like (which includes uv and Rye) out of the box. If you use requirements.in and want deptry to use requirements.txt, you can either pass --requirements-files requirements.txt when invoking deptry, or set the option in pyproject.toml:

[tool.deptry]
requirements_files = ["requirements.txt"]

Features

• Skip type checking blocks when parsing imports (#652)
• Search for requirements.in before requirements.txt on projects using pip requirements format for dependencies (#641)

Bug Fixes

... (truncated)

Changelog

Sourced from deptry's changelog.

0.16.1 - 2024-04-06

Bug Fixes

• Skip type checking blocks whether future annotations are used (#662)

Full Changelog

fpgmaas/deptry@0.16.0...0.16.1

0.16.0 - 2024-04-04

Breaking changes

typing.TYPE_CHECKING handling

Imports guarded by typing.TYPE_CHECKING when using from __future__ import annotations are now skipped. For instance:

from __future__ import annotations
from typing import TYPE_CHECKING
if TYPE_CHECKING:
This import will not be extracted as it is guarded by TYPE_CHECKING and from __future__ import annotations
is used. This means the import should only be evaluated by type checkers, and should not be evaluated during runtime.
import mypy_boto3_s3

See https://deptry.com/usage/#imports-extraction for more information.

requirements.in handling

On projects using pip requirements format for defining dependencies, if requirements_files option is not overridden, deptry will first search for a requirements.in file before requirements.txt, to better support projects using pip-tools and the like (which includes uv and Rye) out of the box. If you use requirements.in and want deptry to use requirements.txt, you can either pass --requirements-files requirements.txt when invoking deptry, or set the option in pyproject.toml:

[tool.deptry]
requirements_files = ["requirements.txt"]

Features

• Skip type checking blocks when parsing imports (#652)
• Search for requirements.in before requirements.txt on projects using pip requirements format for dependencies (#641)

... (truncated)

Commits

• caa4e43 docs(changelog): add 0.16.1 release notes (#668)
• 15c344a chore(deps): lock file maintenance
• a2bfd61 fix(deps): update rust crate serde_json to 1.0.115
• d533f05 chore(deps): update dependency docs/mkdocs-material to v9.5.17
• e187ac9 fix(deps): update rust crate rayon to 1.10.0
• ece7c1a chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.3.5
• 1fa8170 fix(visitor): skip type checking blocks without future annotations (#662)
• 36a06f0 docs(changelog): add 0.16.0 release notes (#657)
• 2ac789f Automatically use requirements.in if the project uses a requirements.txt ...
• 714596c ci: tweak workflows (#658)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[d0choa]

Deptry ignoring TYPECHECKING blocks was the only meaningful change from the changelog:
https://deptry.com/usage/#imports-extraction

Nevertheless, it should cause no issue