Update dependency deptry to ^0.21.0 #117
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.20.0
->^0.21.0
Release Notes
fpgmaas/deptry (deptry)
v0.21.2
Compare Source
Miscellaneous
Full Changelog
v0.21.1
Compare Source
Bug Fixes
setuptools
dynamicdependencies (#945)
Full Changelog
v0.21.0
Compare Source
Breaking changes
Ignore files handling
Unless
--exclude
is used, deptry excludes files found in common ignorefiles (
.gitignore
,.ignore
,$HOME/.config/git/ignore
. ...), by usingignore
Rust crate. The default behaviour has been changed, so that now:
.gitignore
,$HOME/.config/git/ignore
, ...) are only used if deptry is run inside a gitrepository
.gitignore
files that are in parent directories of the git repository from where deptry is run are notused (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 fromrequirements 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:
Configuration
📅 Schedule: Branch creation - "after 5am on saturday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test
.This PR has been generated by MintMaker (powered by Renovate Bot).