Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency deptry to ^0.23.0 #109

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
deptry (changelog) ^0.20.0 -> ^0.23.0 age adoption passing confidence

Release Notes

fpgmaas/deptry (deptry)

v0.23.0

Compare Source

Features
  • Correctly detect transitive dependencies with different module names (#​1033)
Full Changelog

v0.22.0

Compare 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
  • Support PEP 621 in Poetry 2.0+ (#​1003)
Full Changelog

v0.21.2

Compare Source

Miscellaneous
  • Provide wheels for musllinux (#​979)
Full Changelog

v0.21.1

Compare Source

Bug Fixes
  • Handle string requirements files for setuptools dynamic
    dependencies (#​945)
Full Changelog

v0.21.0

Compare Source

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:


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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency deptry to ^0.21.0 Update dependency deptry to ^0.22.0 Jan 10, 2025
@renovate renovate bot force-pushed the renovate/deptry-0.x branch from cbcb3fa to 3e15b66 Compare January 10, 2025 14:56
@renovate renovate bot force-pushed the renovate/deptry-0.x branch from 3e15b66 to 544faa6 Compare January 25, 2025 20:06
@renovate renovate bot changed the title Update dependency deptry to ^0.22.0 Update dependency deptry to ^0.23.0 Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants