Projen Versions Save

Rapidly build modern applications with advanced configuration management

v0.81.7

1 week ago

0.81.7 (2024-05-06)

Features

  • docker-compose: support privileged mode in docker compose (#3553) (7bb3bd9)

v0.81.6

1 week ago

0.81.6 (2024-05-06)

Features

v0.81.5

2 weeks ago

0.81.5 (2024-04-29)

Bug Fixes

v0.81.4

2 weeks ago

0.81.4 (2024-04-28)

Bug Fixes

v0.81.3

2 weeks ago

0.81.3 (2024-04-27)

Bug Fixes

  • release: retrying the workflow can have no effect (#3526) (77e4b7d)

v0.81.2

3 weeks ago

0.81.2 (2024-04-26)

Features

  • dependabot: add target-branch configuration (#3537) (b1af086)

v0.81.1

4 weeks ago

0.81.1 (2024-04-18)

Features

  • update codecov/codecov-action to v4; fixes Node.js 16 deprecation warning (#3531) (9eb1e59), closes #3529

v0.81.0

1 month ago

0.81.0 (2024-04-11)

⚠ BREAKING CHANGES

  • subprojects: by default projen will not be installed in subproject directories. To install projen in a subproject directory, explicitly set projenDevDependency: true in the subproject.

Installing projen in sub-projects leads to weird behavior where the sub-project is referencing different source than the parent project - which breaks things like instanceof expressions when the two class objects are from different sources. I think it makes more sense to only install a single copy of projen for an entire project graph. I suspect that enabling sub-project installation by default was an oversight originally since it makes sense to have that default for the root project. So I think its safe to consider this a non-breaking change since the default will stay unchanged for a root project.

Bug Fixes

  • subprojects: conflicting projenDevDependency is added to subprojects by default (#3506) (c6d17e5), closes #3304

v0.80.20

1 month ago

0.80.20 (2024-04-08)

Bug Fixes

v0.80.19

1 month ago

0.80.19 (2024-04-05)

Bug Fixes

  • upgrade-dependencies: some dependencies are still attempted to be upgraded by ncu, then reverted by projen (#3463) (ab74dab)