You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest two MR's by @mkniewallner (#244 and #245) improved the way that deptry detects configuration files. However, this introduced a change that potentially breaks existing projects that use deptry.
I propose the following release notes:
Breaking changes
Previously, deptry always searched for a pyproject.toml file in the root directory passed as a positional argument to the deptry command. Since this is not in line with what most other tools in the ecosystem do, this is changed in release 0.7.0.
In previous releases, when running:
deptry src
deptry would search for both a pyproject.toml and for python files to scan in the src directory.
Since this release, when running
deptry src
deptry will search for pyproject.toml in the location it is run from, and for python files to scan in the src directory.
The downside of the changes outlined above, is that this could break some projects that did explicitly want to find pyproject.toml in a directory other than the positional argument specified as root. For this purpose, release 0.7.0 adds a --config argument that can be used to explicitly pass the location of pyproject.toml.
Note, in this proposal I also removed the chore(deps) lines, since I think they make the release notes way too cluttered while not adding a lot of important information. Original release notes look like this:
The latest two MR's by @mkniewallner (#244 and #245) improved the way that deptry detects configuration files. However, this introduced a change that potentially breaks existing projects that use deptry.
I propose the following release notes:
Breaking changes
Previously, deptry always searched for a
pyproject.toml
file in the root directory passed as a positional argument to thedeptry
command. Since this is not in line with what most other tools in the ecosystem do, this is changed in release0.7.0
.In previous releases, when running:
deptry would search for both a
pyproject.toml
and for python files to scan in thesrc
directory.Since this release, when running
deptry will search for
pyproject.toml
in the location it is run from, and for python files to scan in thesrc
directory.The downside of the changes outlined above, is that this could break some projects that did explicitly want to find
pyproject.toml
in a directory other than the positional argument specified asroot
. For this purpose, release0.7.0
adds a--config
argument that can be used to explicitly pass the location ofpyproject.toml
.What's Changed
typing
by @mkniewallner in refactor: use generic types instead oftyping
#217ruff
for import sorting and add more rules by @mkniewallner in Useruff
for import sorting and add more rules #232renovate-config-validator
to GH Actions by @mkniewallner in chore: moverenovate-config-validator
to GH Actions #233tox
workflow by @mkniewallner in ci: fixtox
workflow #241pyproject.toml
location fromroot
argument by @mkniewallner in Separatepyproject.toml
location fromroot
argument #244--config
argument by @mkniewallner in Expose and handle--config
argument #245Full Changelog: 0.6.6...0.7.0
Note, in this proposal I also removed the
chore(deps)
lines, since I think they make the release notes way too cluttered while not adding a lot of important information. Original release notes look like this:What's Changed
typing
by @mkniewallner in refactor: use generic types instead oftyping
#217ruff
for import sorting and add more rules by @mkniewallner in Useruff
for import sorting and add more rules #232renovate-config-validator
to GH Actions by @mkniewallner in chore: moverenovate-config-validator
to GH Actions #233tox
workflow by @mkniewallner in ci: fixtox
workflow #241pyproject.toml
location fromroot
argument by @mkniewallner in Separatepyproject.toml
location fromroot
argument #244--config
argument by @mkniewallner in Expose and handle--config
argument #245Full Changelog: 0.6.6...0.7.0
The text was updated successfully, but these errors were encountered: