chore(deps-dev): bump deptry from 0.20.0 to 0.21.2

[dependabot]

Bumps deptry from 0.20.0 to 0.21.2.

Release notes

Sourced from deptry's releases.

0.21.2

What's Changed

Miscellaneous

• Provide wheels for musllinux (#979)

Full Changelog: fpgmaas/deptry@0.21.1...0.21.2

0.21.1

What's Changed

Bug Fixes

• Handle string requirements files for setuptools dynamic dependencies (#945)

Full Changelog: fpgmaas/deptry@0.21.0...0.21.1

0.21.0

What's Changed

Breaking changes

Ignore files handling

Unless --exclude is used, deptry excludes files found in common ignore files (.gitignore, .ignore, $HOME/.config/git/ignore. ...), by using ignore Rust crate. The default behaviour has been changed, so that now:

• git-related ignore rules (.gitignore, $HOME/.config/git/ignore, ...) are only used if deptry is run inside a git repository
• .gitignore files that are in parent directories of the git repository from where deptry is run are not used (previously, deptry would traverse parent directories up to the root system)

If you were using .gitignore files for non-git repositories, you might want to switch to .ignore files, or use --extend-exclude.

Requirements files parsing

deptry now uses requirements-parser to parse dependencies from requirements files, meaning that it can now extract nested requirements files referenced in other requirements files without having to explicitly configure it in deptry.

For instance, if you have:

# requirements.txt
-r cli-requirements.txt
httpx==0.27.2

# cli-requirements.txt
click==8.1.7

With the default configuration, when parsing requirements.txt, both httpx and click will now be listed as dependencies by deptry, while previously, only httpx was, unless deptry was instructed about cli-requirements.txt by using --requirements-files. This new behaviour also impacts development requirements files, that can be overridden by using --requirements-files-dev.

... (truncated)

Changelog

Sourced from deptry's changelog.

0.21.2 - 2024-12-19

Miscellaneous

• Provide wheels for musllinux (#979)

Full Changelog

fpgmaas/deptry@0.21.1...0.21.2

0.21.1 - 2024-11-15

Bug Fixes

• Handle string requirements files for setuptools dynamic dependencies (#945)

Full Changelog

fpgmaas/deptry@0.21.0...0.21.1

0.21.0 - 2024-11-08

Breaking changes

Ignore files handling

Unless --exclude is used, deptry excludes files found in common ignore files (.gitignore, .ignore, $HOME/.config/git/ignore. ...), by using ignore Rust crate. The default behaviour has been changed, so that now:

• git-related ignore rules (.gitignore, $HOME/.config/git/ignore, ...) are only used if deptry is run inside a git repository
• .gitignore files that are in parent directories of the git repository from where deptry is run are not used (previously, deptry would traverse parent directories up to the root system)

If you were using .gitignore files for non-git repositories, you might want to switch to .ignore files, or use --extend-exclude.

Requirements files parsing

deptry now uses requirements-parser to parse dependencies from requirements files, meaning that it can now extract nested requirements files referenced in other requirements files without having to explicitly configure it in deptry.

For instance, if you have:

</tr></table> 

... (truncated)

Commits

• 816a069 docs(changelog): add 0.21.2 release notes (#981)
• 6b4c781 ci: publish musl wheels for Linux (#979)
• 5fc0390 chore: add zizmor-pre-commit to limit GH Actions vulnerabilities (#972)
• 14cede0 chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.8.3 (#974)
• 72fa7fb chore(deps): lock file maintenance (#976)
• 20aff15 chore(deps): update uv-version to v0.5.9 (#975)
• ccda627 chore(deps): update dependency mkdocs-material to v9.5.48 (#973)
• df1025b chore(deps): update dependency pytest to v8.3.4 (#968)
• 96992c9 chore(deps): lock file maintenance (#971)
• 76e2a0c chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.8.2 (#969)
• 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)