1.7.0 prep (#3057)

* Fix indent level in documentation

* Update release testing procedure

* Prepare release 1.7.0

* Revert signing of the self-executable ktlint file

Temporarily revert the Gradle configuration cache to unblock the release

Author: paul-dingemans

CHANGELOG.md

@@ -2,6 +2,92 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](https://semver.org/).
 
+## [1.7.0] - 2025-07-14
+
+### 🆕 Features
+
+#### Context receiver / parameters
+
+With upgrade to Kotlin 2.2.0, Ktlint 1.7.0 supports context parameters. 
+
+* Add `context-receiver-list-wrapping` rule - [#3034](https://github.com/pinterest/ktlint/pull/3034), by @paul-dingemans
+
+* Add context receiver list to `modifier-order` rule - [#3031](https://github.com/pinterest/ktlint/pull/3031), by @paul-dingemans
+
+* Ignore context parameters in rule `context-receiver-wrapping` - [#3033](https://github.com/pinterest/ktlint/pull/3033), by @paul-dingemans
+
+#### Other rule changes
+
+* Do not run `no-unused-imports` rule by default - [#3039](https://github.com/pinterest/ktlint/pull/3039), by @paul-dingemans  
+  The `no-unused-import` rule is no longer run by default as it keeps causing problems. It will be removed in Ktlint `2.0`. Until then, the rule can still be run, when enabled explicitly in `.editorconfig`.
+
+* Add experimental rule `expression-operand-wrapping` - [#3056](https://github.com/pinterest/ktlint/pull/3056), by @paul-dingemans  
+  This rule aligns wrapping of arithmetic and logical multiline expressions. The `condition-wrapping` rule which did something similar for logical multiline expressions only no longer reports and fixes violations. It will be removed in Ktlint `2.0`.
+
+#### Other features
+
+* Deprecate functions in `ASTNodeExtensions`, and where applicable provide property accessors - [#3026](https://github.com/pinterest/ktlint/pull/3026), by @paul-dingemans  
+  When using `ASTNodeExtensions` please replace function calls with the new (temporary) property accessors. The temporary property accessors are needed to maintain backwards compatability with Java integration. In Ktlint `2.0` the functions will be removed, and the temporary property accessors will be replaced with final names. 
+
+* Suppress warning "sun.misc.Unsafe::objectFieldOffset" in Ktlint CLI (Java24+) - [#3040](https://github.com/pinterest/ktlint/pull/3040), by @paul-dingemans
+
+* Suppress error "A restricted method in java.lang.System has been called" on Java 24 in KtLint CLI only - [#3043](https://github.com/pinterest/ktlint/pull/3043), by @paul-dingemans
+
+* Remove unneeded "--add-opens=java.base/java.lang=ALL-UNNAMED" - [#3044](https://github.com/pinterest/ktlint/pull/3044), by @paul-dingemans
+
+
+### 🔧 Fixes
+
+
+* Do not remove an empty value parameter list from a call expression when it is nested - [#3017](https://github.com/pinterest/ktlint/pull/3017), by @paul-dingemans
+
+* Clarify violation message in `filename` rule - [#3046](https://github.com/pinterest/ktlint/pull/3046), by @paul-dingemans
+
+### 📦 Dependencies
+
+
+* chore(deps): update plugin org.gradle.toolchains.foojay-resolver-convention to v1 - [#2989](https://github.com/pinterest/ktlint/pull/2989), by @renovate[bot]
+
+* chore(deps): update plugin com.gradle.develocity to v4.0.2 - [#2996](https://github.com/pinterest/ktlint/pull/2996), by @renovate[bot]
+
+* fix(deps): update junit5 monorepo - [#3005](https://github.com/pinterest/ktlint/pull/3005), by @renovate[bot]
+
+* fix(deps): update dependency org.jetbrains.kotlin:kotlin-gradle-plugin to v2.2.0-rc3 - [#3015](https://github.com/pinterest/ktlint/pull/3015), by @renovate[bot]
+
+* fix(deps): update dependency org.junit.jupiter:junit-jupiter to v5.13.2 - [#3020](https://github.com/pinterest/ktlint/pull/3020), by @renovate[bot]
+
+* fix(deps): update dependency org.junit.platform:junit-platform-launcher to v1.13.2 - [#3021](https://github.com/pinterest/ktlint/pull/3021), by @renovate[bot]
+
+* fix(deps): update kotlin monorepo to v2.2.0 - [#3018](https://github.com/pinterest/ktlint/pull/3018), by @renovate[bot]
+
+* chore(deps): update plugin shadow to v8.3.8 - [#3030](https://github.com/pinterest/ktlint/pull/3030), by @renovate[bot]
+
+* fix(deps): update junit-framework monorepo - [#3037](https://github.com/pinterest/ktlint/pull/3037), by @renovate[bot]
+
+* chore(deps): update plugin kotlinx-binary-compatibiltiy-validator to v0.18.1 - [#3050](https://github.com/pinterest/ktlint/pull/3050), by @renovate[bot]
+
+* fix(deps): update dependency dev.drewhamilton.poko:poko-gradle-plugin to v0.19.1 - [#3053](https://github.com/pinterest/ktlint/pull/3053), by @renovate[bot]
+
+* fix(deps): update dependency com.google.jimfs:jimfs to v1.3.1 - [#3054](https://github.com/pinterest/ktlint/pull/3054), by @renovate[bot]
+
+* chore(deps): update dependency gradle to v9.0.0-rc-2 - [#3055](https://github.com/pinterest/ktlint/pull/3055), by @renovate[bot]
+
+### 💬 Other
+
+* Update publishing URLs to point to Central Portal OSSRH staging API - [#3006](https://github.com/pinterest/ktlint/pull/3006), by @shashachu
+
+* Update publishing credentials to use new Central Portal username/token - [#3007](https://github.com/pinterest/ktlint/pull/3007), by @shashachu
+
+* Improve build - [#3025](https://github.com/pinterest/ktlint/pull/3025), by @mateuszkwiecinski
+
+* Bump `poko-gradle-plugin` with a workaround (enforce compatible Kotlin version) - [#3035](https://github.com/pinterest/ktlint/pull/3035), by @mateuszkwiecinski
+
+* Java 24 - [#3049](https://github.com/pinterest/ktlint/pull/3049), by @paul-dingemans
+
+* Make `build-logic` plugins expose binary plugins - [#3047](https://github.com/pinterest/ktlint/pull/3047), by @mateuszkwiecinski
+
+* Cleanup Java 24 bump  - [#3051](https://github.com/pinterest/ktlint/pull/3051), by @mateuszkwiecinski
+
 ## [1.6.0] - 2025-05-19
 
 🆕 Features
@@ -2716,6 +2802,7 @@ set in `[*{kt,kts}]` section).
 
 ## 0.1.0 - 2016-07-27
 
+[1.7.0]: https://github.com/pinterest/ktlint/compare/1.7.0...1.6.0
 [1.6.0]: https://github.com/pinterest/ktlint/compare/1.6.0...1.5.0
 [1.5.0]: https://github.com/pinterest/ktlint/compare/1.5.0...1.4.1
 [1.4.1]: https://github.com/pinterest/ktlint/compare/1.4.1...1.4.0

RELEASE_TESTING.MD

@@ -40,7 +40,7 @@ Before releasing a new version of KtLint, the release candidate is tested on a s
    ```
 4. Create an alias or script to run the latest released version of ktlint (note that this script will print the version as reference to which version is used):
    ```shell
-   alias ktlint-prev="ktlint-1.3.1 $@" # Replace with the latest release version
+   alias ktlint-prev="ktlint-1.6.0 $@" # Replace with the latest release version
    ```
    Note that `~/git/ktlint` is the directory in which the ktlint project is checked out and that `~/git/ktlint/ktlint` refers to the `ktlint` CLI-module.
 5. Create an alias or script to run the latest development-version of ktlint (note that this script will print the version and the datetime of compilation as reference to which version is used):
@@ -99,7 +99,7 @@ Formatting projects in which ktlint is not used may result in a huge amount of f
    ```shell
    ./exec-in-each-project.sh "git add --all && git commit -m \"Update .editorconfig to fallback to integration test settings\""
    ```
-3. Format with previous (*latest released*) version of Lint
+3. Format with previous (*latest released*) version of KtLint
    ```shell
    ktlint-prev --format --relative # Do not call this command via the "./exec-in-each-project.sh" script.
    ```
@@ -108,13 +108,13 @@ Formatting projects in which ktlint is not used may result in a huge amount of f
    ```shell
    ./exec-in-each-project.sh "git add --all && git commit -m \"Format with previous ktlint version (round #)\""
    ```
-   Repeat step 4 and 5 until no files are changed anymore. Although ktlint reruns up to 3 times in case new violations are introduced, it can still happen that not all violations have been fixed with a single invocation.
+   Repeat step 3 and 4 until no files are changed anymore. Although ktlint reruns up to 3 times in case new violations are introduced, it can still happen that not all violations have been fixed with a single invocation.
 5. Build baseline file with previous (*latest released*) version of Lint (when building with format the offsets of the error are not saved correctly in the baseline) so that all errors which cannot be autocorrected are ignored.
    ```shell
    rm baseline.xml
    ktlint-prev --baseline=baseline.xml --relative # Do not call this command via the "./exec-in-each-project.sh" script.
    ```
-   Note: Ignore all output as this is the old version! Inspect the baseline roughly to verify that it only contains errors that cannot be autocorrected. 
+   Note: Ignore all output as this is the old version! Inspect the baseline roughly to verify that it only contains errors that cannot be autocorrected.
 6. Format the sample projects with the previous (*latest released*) ktlint version:
    ```shell
    ktlint-prev -F --baseline=baseline.xml --relative # Do not call this command via the "./exec-in-each-project.sh" script.
@@ -147,8 +147,8 @@ Formatting projects in which ktlint is not used may result in a huge amount of f
    * Usually it helps to disable all rules that emit violations, except one of those rules. In this way it is possible to evaluate the changes rule by rule.
    * Ideally, no violations are shown. This means that all violations have been autocorrected. Note that violations might pop up that previously were suppressed via the baseline. This can happen as due to code changes, the references in the baseline.xml no longer match with the positions where they occur. First check the code changes, and regenerating the baseline before verifying the next can be a helpful approach.
    * 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.
-10. 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:
+   * If a violation is shown which is not marked as being "cannot 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.
+10. 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\""
     ```

documentation/snapshot/docs/rules/experimental.md

@@ -125,7 +125,7 @@ Suppress or disable rule (1)
     ktlint_standard_blank-line-between-when-conditions = disabled
     ```
 
-### Expression operand wrapping
+## Expression operand wrapping
 
 Wraps each operand in a multiline expression to a separate line.
 

gradle.properties

@@ -1,4 +1,4 @@
-VERSION_NAME=1.6.1-SNAPSHOT
+VERSION_NAME=1.7.0
 POM_GROUP_ID=com.pinterest.ktlint
 
 POM_DESCRIPTION=An anti-bikeshedding Kotlin linter with built-in formatter.
@@ -20,7 +20,7 @@ POM_DEVELOPER_NAME=Pinterest, Inc.
 org.gradle.jvmargs=-Xmx4g
 org.gradle.parallel=true
 org.gradle.caching=true
-org.gradle.configuration-cache=true
+org.gradle.configuration-cache=false
 org.gradle.configuration-cache.parallel=true
 
 # Use V2 of the Dokka library and silence its warnings

ktlint-cli/build.gradle.kts

@@ -74,11 +74,6 @@ val shadowJarExecutable by tasks.registering(DefaultTask::class) {
     outputs.files(selfExecutableKtlintSignatureOutputPath)
     outputs.files(windowsBatchFileOutputPath)
 
-    if (signing.isRequired) {
-        logger.lifecycle("Creating the signature file: $selfExecutableKtlintSignatureOutputPath")
-        signing.sign(selfExecutableKtlintSignatureOutputPath)
-    }
-
     doLast {
         selfExecutableKtlintOutputPath.apply {
             logger.lifecycle("Creating the self-executable file: $selfExecutableKtlintOutputPath")
@@ -110,6 +105,11 @@ val shadowJarExecutable by tasks.registering(DefaultTask::class) {
             appendBytes(ktlintCliAllJarFile.readBytes())
 
             setExecutable(true, false)
+
+            if (signing.isRequired) {
+                logger.lifecycle("Creating the signature file: $selfExecutableKtlintSignatureOutputPath")
+                signing.sign(this)
+            }
         }
         logger.lifecycle("Creating the batch file for Windows OS: $windowsBatchFileOutputPath")
         windowsBatchFileOutputPath.writeText(windowsBatchFileInputPath.readText())