Releases: DavidVujic/python-polylith
feat(poetry): dependency constrain support for Poetry 2
Adding support for Poetry 2. The Polylith Poetry plugin did have dependency constraint set to v1 of Poetry. With this update, it should be possible to upgrade the Poetry version to the latest (v2).
Details in #315
feat(poly build): setup and teardown for building, when using Maturin or tools without hook or plugin support
Support for additional Package & Dependency Management tools, primarily Maturin.
Adding a new command - poly build - that can be used for building wheels when deploying projects from a Polylith Workspace when the underlying tool doesn't have any hook or plugin support.
Details in #299
fix: hatchling dev-mode projects with editable installs
Fixes an issue that appeared for Hatch and Uv users after the release of the Hatch build hook v1.3.0.
Details in #308
feat(hatch): add support for editable installs
Details in #306
Note: the feature is only partially done with this release.
fix(workspace root): check if path exist
Fixes an issue with failing to locate the workspace root, when the Polylith Workspace is in a sub-folder and not using the workspace.toml for the Polylith-specific config.
Details in #305
feat: find workspace root for repos with several sub-workspaces
Find the Workspace root for repos containing the Polylith workspace in a sub-directory, and the use case when not using the workspace.toml to configure the workspace.
Details in #296
feat(poly check): verbose output without duplication, with coloring
feat(poly diff): changed bricks when the Polylith Workspace is in a subfolder of the repo
Add support for monorepos with the Polylith Workspace in a subfolder.
Before, the poly diff command would fail finding any changes, because of the mismatch between the underlying git diff and the workspace folder stucture.
Details in #289
fix: allow Python 3.8 in Hatch build hook
Details in #285
feat(poetry plugin): add support for upcoming Poetry PEP 621 projects
Adding support for the upcoming Poetry release - that will be PEP 621 compliant - for those Poetry projects that will use the PEP 621 standard to define project metadata and dependencies.
Details in #278