2.30.0

No documented user facing changes

2.29.0

Type	Description	Link
Fix	Stop using the Save Actions plugin (broken in IntelliJ 2023.1) and use native format on save (requires IntelliJ >=2021.2)	#862

2.28.0

Type	Description	Link
Fix	Write configuration to IPR file if it exists, as well as the .idea directory, to avoid errors in legacy projects	#810

2.27.0

Type	Description	Link
Improvement	Use bootstrapping formatter starting from Intellij 2022.2	#798

2.26.0

Type	Description	Link
Improvement	Support ea versions of Java	#784

2.25.0

Type	Description	Link
Fix	Fix problems on windows	#772

2.24.0

Type	Description	Link
Improvement	Publish gradle plugin to gradle plugin portal	#731

2.23.0

Type	Description	Link
Improvement	Fix lambda compactness regression	#728

2.22.0

Type	Description	Link
Fix	Only apply line break to lambdas with statements ## Before this PR Previous PR #707 was a little aggressive and inserted line breaks for non-statement lambdas. ## After this PR Only multi-line lambdas cause a line-break in the method chain.	#708

2.21.0

Type	Description	Link
Improvement	Break on lambda argument in method chain ## Before this PR Chained calls involving lambda expressions don't line break, which conflicts with checkstyle (at least the gradle-baseline checkstyle config) java<br>class PalantirLambdaInliningPrefersBreak {<br> void foo() {<br> return hello.read(txn -> {<br> doSomeWork();<br> doSomeMoreWork();<br> })<br> .chainedCall(() -> {<br> doSomeWork();<br> });<br> }<br>}<br><br> ## After this PR java<br>class PalantirLambdaInliningPrefersBreak {<br> void foo() {<br> return hello<br> .read(txn -> {<br> doSomeWork();<br> doSomeMoreWork();<br> })<br> .chainedCall(() -> {<br> doSomeWork();<br> });<br> }<br>}<br> ## Possible downsides? 🤷‍♂️ I've also added a test to show that non-chained lambda calls don't include a line break	#707