Merge pull request #2495 from pinterest/1.1.1-prep

Prepare 1.1.1 release

CHANGELOG.md

@@ -2,15 +2,44 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](https://semver.org/).
 
-## [Unreleased]
+## [1.1.1] - 2024-01-08
 
-### Added
+### 🆕 Features
 
-### Removed
+None
 
-### Fixed
+### 🔧 Fixes
 
-### Changed
+
+* Fix incorrect generateEditorConfig example in documentation - [#2444](https://github.com/pinterest/ktlint/pull/2444), by @stay7
+
+* Fix insert of suppression on binary expression - [#2463](https://github.com/pinterest/ktlint/pull/2463), by @paul-dingemans
+
+* Loosen dependency between chain-method-continuation and argument-list-wrapping - [#2468](https://github.com/pinterest/ktlint/pull/2468), by @paul-dingemans
+
+* Keep arrow when both parameter list and block of function literal are empty - [#2469](https://github.com/pinterest/ktlint/pull/2469), by @paul-dingemans
+
+* Improve wrapping of binary expressions - [#2479](https://github.com/pinterest/ktlint/pull/2479), by @paul-dingemans
+
+* Resolve conflict between parameter-list-spacing and parameter-list-wrapping - [#2491](https://github.com/pinterest/ktlint/pull/2491), by @paul-dingemans
+
+* Do not wrap binary expression value argument if it is already preceded by a newline - [#2493](https://github.com/pinterest/ktlint/pull/2493), by @paul-dingemans
+
+* Fix operator spacing - [#2473](https://github.com/pinterest/ktlint/pull/2473), by @paul-dingemans
+
+* Run `argument-list-wrapping`, `class-signature` and `function-signature` when comment rules are disabled - [#2466](https://github.com/pinterest/ktlint/pull/2466), by @paul-dingemans
+
+### 📦 Dependencies
+
+* fix(deps): update kotlin monorepo to v1.9.22 - [#2456](https://github.com/pinterest/ktlint/pull/2456), by @renovate[bot]
+
+* chore(deps): update actions/setup-python action to v5 - [#2417](https://github.com/pinterest/ktlint/pull/2417), by @renovate[bot]
+
+* fix(deps): update dependency org.slf4j:slf4j-simple to v2.0.10 - [#2470](https://github.com/pinterest/ktlint/pull/2470), by @renovate[bot]
+
+* fix(deps): update dependency dev.drewhamilton.poko:poko-gradle-plugin to v0.15.2 - [#2485](https://github.com/pinterest/ktlint/pull/2485), by @renovate[bot]
+
+* fix(deps): update dependency org.assertj:assertj-core to v3.25.1 - [#2486](https://github.com/pinterest/ktlint/pull/2486), by @renovate[bot]
 
 ## [1.1.0] - 2023-12-19
 
@@ -2272,6 +2301,7 @@ set in `[*{kt,kts}]` section).
 
 ## 0.1.0 - 2016-07-27
 
+[1.1.1]: https://github.com/pinterest/ktlint/compare/1.1.1...1.1.0
 [1.1.0]: https://github.com/pinterest/ktlint/compare/1.0.1...1.1.0
 [1.0.1]: https://github.com/pinterest/ktlint/compare/1.0.0...1.0.1
 [1.0.0]: https://github.com/pinterest/ktlint/compare/0.50.0...1.0.0

RELEASE_TESTING.MD

@@ -134,13 +134,13 @@ Formatting projects in which ktlint is not used may result in a huge amount of f
    ktlint-dev -F --baseline=baseline.xml --relative # Do not call this command via the "./exec-in-each-project.sh" script as we want to use the one combined baseline.xml file for all projects.
    ```
    Inspect the output carefully:
-  * If you see an error like below, then this version obviously may *not* be released. It is best to fix this error before continuing with testing and validating!
+   * If you see an error like below, then this version obviously may *not* be released. It is best to fix this error before continuing with testing and validating!
     ```plain
     Internal Error (...) in file '...' at position '0:0. Please create a ticket at https://github.com/pinterest/ktlint/issues ...
     ```
-  * Ideally, no violations are shown. This means that all violations have been autocorrected.
-  * Violations which could not be autocorrected should be validated for correctness but do not block the release as most likely this is intended behavior.
-  * If a violation is shown which is not marked as being "can not be autocorrected" this means that during autocorrect of another violation a new violations has been introduced. This should be fixed before releasing especially when the next format introduces the original violation again which of course would result in an endless loop.
+   * Ideally, no violations are shown. This means that all violations have been autocorrected.
+   * Violations which could not be autocorrected should be validated for correctness but do not block the release as most likely this is intended behavior.
+   * If a violation is shown which is not marked as being "can not be autocorrected" this means that during autocorrect of another violation a new violations has been introduced. This should be fixed before releasing especially when the next format introduces the original violation again which of course would result in an endless loop.
 8. Inspect all fixed violations, Of course inspection similar violations tens of times does not make sense. At least check different types of violations a couple of times. Commit changes which do not need to be inspected again:
    ```shell
    ./exec-in-each-project.sh "git add --all && git commit -m \"Fixed with latest development version\""

gradle.properties

@@ -1,4 +1,4 @@
-VERSION_NAME=1.2.0-SNAPSHOT
+VERSION_NAME=1.1.1
 POM_GROUP_ID=com.pinterest.ktlint
 
 POM_DESCRIPTION=An anti-bikeshedding Kotlin linter with built-in formatter.