Releases: bneijt/poetry-lock-package
Bugfix support for multiple marked version constraints
What's Changed
If we have a list of possible versions with markers on each version range, we ignore the markers. This could, very unlikely, lead to versioning issues (for example, if we have a platform marker and a multi-version constraint from a package), but the likelihood is very small.
Full Changelog: 0.5.0...0.5.1
Filter metadata to support poetry lock version 2
Poetry 1.3.1 uses poetry lock version 2 which adds a files entry to the metadata in the dependencies.
This new version or poetry lock package will pick a subset of dependency attributes from the lock file, instead of using everything that is there. We might miss a field, so this is considered a minor upgrade and not a bugfix release.
Add build-system configuration to lock-package
Adds a build-system section to the lock package pyproject.toml.
Does not change anything for people running with --build
, just for those who generate the project and want to inspect/move it from there.
What's Changed
New Contributors
Full Changelog: 0.4.4...0.4.5
Bugfix: only use minimal parent project attributes for lock package
This release closes issue #24 where some attributes where copied to the lock package project that should not be.
The generation of the lock project approach has changed to only include some attributes instead of deleting unwanted attributes.
This is a behavior change, if you miss any attributes in the generated package, please open a Github issue.
Bugfix: don't apply markers if package is a root dependency
If the project requires a package A and package B and package B only requires package A with a marker, then the lock package should not require A with a marker as B suggests, but A directory without applying markers requested from B for package A.
Bugfix: allow for src subfolder in root project
Bugfix: normalize package names on matching
This is a bugfix to fix matching the lock package name to the project package name, when the project package name has been added using a different form (adding pybluez
instead of PyBluez
)
Taking off those dependencies
This release drops most dependencies (click and loguru) to make it easier to integrate the project in a dev environment.
This release also renames the --no-parent
option to --no-root
, which aligns the naming with what poetry install
calls it.
This release closes: #14
Add --build option
You can use the --build
flag, to build and clean automatically, leaving you with a lock package in the dist folder of your current project.
Ignore on all levels
Ignore will not work on lower levels. This means that if a dependency is only a dependency of an ignored package, it will not be part of the lock package dependencies.