Update dependency deptry to ^0.25.0#117
Open
red-hat-konflux[bot] wants to merge 1 commit intomainfrom
Open
Conversation
bd4ff67 to
bf0cb41
Compare
bf0cb41 to
b2256fc
Compare
b2256fc to
640ae20
Compare
640ae20 to
f658271
Compare
f658271 to
b57c8f5
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
b57c8f5 to
1ddf31f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.25.0Release Notes
osprey-oss/deptry (deptry)
v0.25.1Compare Source
Release 0.25.0 was yanked in PyPI because of a failure during the release. 0.25.1 is identical, but includes a fix in the release process.
v0.25.0Compare Source
Repository moved to Osprey OSS
deptry has moved from fpgmaas/deptry to osprey-oss/deptry under the new Osprey OSS organisation. This ensures the project is not tied to a single account and makes it easier to manage contributors and access as the project grows.
Features
# deptry: ignorecomments to suppress violations (#1473)--non-dev-dependency-groups(#1440)tomlion Python < 3.15 for TOML 1.1 support (#1446)--optional-dependencies-dev-groupsand deprecate--pep621-dev-dependency-groups(#1391)Bug Fixes
--configdoes not suppress output (#1390)Full Changelog
v0.24.0Compare Source
Breaking changes
Python 3.9 support dropped
Support for Python 3.9 has been dropped, as it has reached its end of life.
PyPy 3.10 support dropped, 3.11 added
Support for PyPy 3.10 has been dropped, since it is unsupported. We now only test against PyPy 3.11, and only publish wheels for this version.
Features
Full Changelog
v0.23.1Compare Source
Bug Fixes
TYPE_CHECKINGblocks by supportingimport typing as tand checkingt.TYPE_CHECKING(#1218)Full Changelog
v0.23.0Compare Source
Features
Full Changelog
v0.22.0Compare Source
Poetry 2.0 introduced support
for defining project metadata in PEP 621. This is now
supported by deptry. Documentation has been updated to
detail deptry's behavior.
Features
Full Changelog
v0.21.2Compare Source
Miscellaneous
Full Changelog
v0.21.1Compare Source
Bug Fixes
setuptoolsdynamicdependencies (#945)
Full Changelog
v0.21.0Compare Source
Breaking changes
Ignore files handling
Unless
--excludeis used, deptry excludes files found in common ignorefiles (
.gitignore,.ignore,$HOME/.config/git/ignore. ...), by usingignoreRust 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
.gitignorefiles 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
.gitignorefiles for non-git repositories, you might want to switch to.ignorefiles, or use--extend-exclude.Requirements files parsing
deptry now uses
requirements-parserto 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:
With the default configuration, when parsing
requirements.txt, bothhttpxandclickwill now be listed asdependencies by deptry, while previously, only
httpxwas, unless deptry was instructed aboutcli-requirements.txtby using--requirements-files. This newbehaviour also impacts development requirements files, that can be overridden by
using
--requirements-files-dev.Python 3.8 support dropped
Support for Python 3.8 has been dropped, as it has reached its end of life.
Features
[dependency-groups]section, introducedby PEP 735 (#892)
setuptoolsdynamic dependencies set in[tool.setuptools.dynamic]section,see https://deptry.com/supported-dependency-managers/#setuptools for more
details (#894, #724)
requirements-parser, adding support for parsing nested requirementsfiles referenced with
-r <requirement_file>(#913)Full Changelog
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.