Skip to content

Releases: DavidVujic/python-polylith

fix: brick usage via interface, remove circular brick dependencies

Choose a tag to compare

@DavidVujic DavidVujic released this 04 Jul 10:28
1441411

Removing brick interface bypassing, and circular references that was reported by the poly deps --interface command for the Polylith workspace itself.

Details in #456

fix(hatchling): allow any minor version for v1

Choose a tag to compare

@DavidVujic DavidVujic released this 03 Jul 10:10
db142fa

Allow any v1 version of hatchling to be used.

Details in #453 and #454

fix: set the used rich library to a wildcard version

Choose a tag to compare

@DavidVujic DavidVujic released this 03 Jul 09:45
1512b92

Setting * as the version for rich to avoid any versioning conflicts with the projects themselves using it.

Details in #452

fix(skills): add a polylith- prefix for all the migration skills

Choose a tag to compare

@DavidVujic DavidVujic released this 07 Jun 11:16
e11d0ae

Adding a polylith- prefix to all the migration skills, to avoid any name collisions with other skills. Also: to align with how the library-skills package adds the symlinks to projects (flat, and not per project).

Details in #448

feat(skills): add migrate-project-to-polylith skills

Choose a tag to compare

@DavidVujic DavidVujic released this 07 Jun 10:56
8ccaf06

Adding skills for migrating non-Polylith Python projects into a Polylith workspace. These skills are included in the polylith-cli releases.

Details in #447

fix(CLI): update the Agent skills readme

Choose a tag to compare

@DavidVujic DavidVujic released this 06 May 20:46
0ac7301

Removing a redundant section from the humans-only README.

Details in #446

feat: add agent skills

Choose a tag to compare

@DavidVujic DavidVujic released this 05 May 21:39
fe5bba5

Adding agent skills for the tool, including the basic concepts of the Polylith Architecture.

The skills are included in the CLI - and as direct downloads from this repo (the .agents folder).

Details in #442 and #444

feat(poly create project): quiet option does not trigger interactive mode

Choose a tag to compare

@DavidVujic DavidVujic released this 05 May 06:26
9e875ad

Adding support for a --quiet option for the poly create project command. This option will not trigger any interactive mode (i.e. not asking to add a base if available).

This option is useful for agents when runing the poly tool.

Details in #443

fix(poly info): for Poetry with PEP-621 support

Choose a tag to compare

@DavidVujic DavidVujic released this 18 Apr 14:41
f7d2353

Fixing an issue for Poetry users that have their pyproject.toml files set up according to PEP-621.

Details in #440

fix(poly sync): for Poetry with PEP-621 support

Choose a tag to compare

@DavidVujic DavidVujic released this 18 Apr 14:15
586c6c2

Fixing an issue with poly sync for Poetry users, and when the pyprojec.toml is according to PEP-621.

Details in #439