Skip to content

Update dependency com.palantir.javaformat:palantir-java-format to v2.102.0 - #3132

Merged
nedtwigg merged 4 commits into
mainfrom
renovate/com.palantir.javaformat-palantir-java-format-2.x
Oct 8, 2026
Merged

nedtwigg merged 4 commits into
mainfrom
renovate/com.palantir.javaformat-palantir-java-format-2.x

Conversation

@renovate

@renovate renovate Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
com.palantir.javaformat:palantir-java-format 2.99.0 → 2.102.0 age confidence

Warning

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


Release Notes

palantir/palantir-java-format (com.palantir.javaformat:palantir-java-format)

v2.102.0

Compare Source

💡 Improvements
  • Disable GPG signing in test repository (#​1814)

Full Changelog: 2.101.0...2.102.0

v2.101.0

Compare Source

No documented user-facing changes

Full Changelog: 2.100.0...2.101.0

v2.100.0

Compare Source

🐛 Fixes
  • Allow Java Format without Spotless (#​1755)

Full Changelog: 2.99.0...2.100.0


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

renovate Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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.3', 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.10.
        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.6 > org.gradle.kotlin:gradle-kotlin-dsl-plugins:6.7.6
         > Repository Gradle Central Plugin Repository is disabled due to earlier error below:
            > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugins-bom:2.4.10.
               > Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.10/kotlin-gradle-plugins-bom-2.4.10.pom'.
                  > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.10/kotlin-gradle-plugins-bom-2.4.10.pom'.
                     > Received status code 429 from server: Too Many Requests
      > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.4.10.
        Required by:
            buildscript of project ':build-logic' > org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:6.7.6 > org.gradle.kotlin:gradle-kotlin-dsl-plugins:6.7.6
         > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.4.10.
            > Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugin-api/2.4.10/kotlin-gradle-plugin-api-2.4.10.pom'.
               > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugin-api/2.4.10/kotlin-gradle-plugin-api-2.4.10.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 35s

@renovate
renovate Bot force-pushed the renovate/com.palantir.javaformat-palantir-java-format-2.x branch from 350d5fa to e4fa52f Compare October 8, 2026 20:19
@renovate renovate Bot changed the title Update dependency com.palantir.javaformat:palantir-java-format to v2.101.0 Update dependency com.palantir.javaformat:palantir-java-format to v2.102.0 Oct 8, 2026
@renovate

renovate Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor Author

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.

@nedtwigg

nedtwigg commented Oct 8, 2026

Copy link
Copy Markdown
Member

@Goooler take a look at 7742abc, it would be nice if the magic changelog task could handle this case

@nedtwigg
nedtwigg enabled auto-merge October 8, 2026 20:26
@nedtwigg
nedtwigg merged commit 1c93df4 into main Oct 8, 2026
32 checks passed
@nedtwigg
nedtwigg deleted the renovate/com.palantir.javaformat-palantir-java-format-2.x branch October 8, 2026 20:51
@Goooler

Goooler commented Oct 8, 2026

Copy link
Copy Markdown
Member

it would be nice if the magic changelog task could handle this case

It's a bit annoying to my side. The current implementation could detect all actual version changes from HEAD, I don't think we need to note all the changed steps in the items.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants