Update dependency io.cucumber:gherkin to v42.0.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
io.cucumber:gherkin	42.0.0 → 42.0.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

cucumber/gherkin (io.cucumber:gherkin)

v42.0.1

Added

• [Java] Added builder option to use non-deprecated IdGenerator.

Fixed

• [Java] Use version range for org.jspecify:jspecify

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: gradle/libs.versions.toml

Command failed: ./gradlew -Dorg.gradle.jvmargs=-Xms512m -Xmx512m --console=plain --dependency-verification lenient -q properties

FAILURE: Build failed with an exception.

* Where:
Settings file '/tmp/renovate/repos/github/diffplug/spotless/settings.gradle.kts' line: 9

* What went wrong:
Error resolving plugin [id: 'com.diffplug.spotless', version: '8.10.2', apply: false]
> A problem occurred configuring project ':build-logic'.
   > Could not resolve all artifacts for configuration 'classpath'.
      > Could not resolve org.jetbrains.kotlin:kotlin-stdlib:2.4.0.
        Required by:
            buildscript of project ':build-logic'
            buildscript of project ':build-logic' > org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:6.7.3 > org.gradle.kotlin:gradle-kotlin-dsl-plugins:6.7.3
         > Repository Gradle Central Plugin Repository is disabled due to earlier error below:
            > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugins-bom:2.4.0.
               > Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.0/kotlin-gradle-plugins-bom-2.4.0.pom'.
                  > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.0/kotlin-gradle-plugins-bom-2.4.0.pom'. Received status code 429 from server: Too Many Requests
      > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.4.0.
        Required by:
            buildscript of project ':build-logic' > org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:6.7.3 > org.gradle.kotlin:gradle-kotlin-dsl-plugins:6.7.3
         > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.4.0.
            > Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugin-api/2.4.0/kotlin-gradle-plugin-api-2.4.0.pom'.
               > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugin-api/2.4.0/kotlin-gradle-plugin-api-2.4.0.pom'. Received status code 429 from server: Too Many Requests
> There are 3 more failures with identical causes.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights from a Build Scan (powered by Develocity).
> Get more help at https://help.gradle.org.

BUILD FAILED in 46s

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.