Skip to content

Fix Micrometer 1.17.1 JSpecify convergence - #1560

Closed
skrcode wants to merge 1 commit into
apache:dependabot/maven/io.micrometer-micrometer-core-1.17.1from
skrcode:jaipilot/micrometer-jspecify-convergence
Closed

Fix Micrometer 1.17.1 JSpecify convergence#1560
skrcode wants to merge 1 commit into
apache:dependabot/maven/io.micrometer-micrometer-core-1.17.1from
skrcode:jaipilot/micrometer-jspecify-convergence

Conversation

@skrcode

@skrcode skrcode commented Aug 30, 2026

Copy link
Copy Markdown

Why

This is a companion to #1558. Micrometer 1.17.1 brings JSpecify 1.0.1 while the OpenRewrite test toolchain still resolves JSpecify 1.0.0, so Maven Enforcer rejects the wicket-migration dependency graph.

What changed

Manage org.jspecify:jspecify at 1.0.1 in the wicket-migration test dependency management section. The override is deliberately scoped to the module and test toolchain where the convergence conflict occurs.

Verification

  • JDK 25: mvn -B --no-transfer-progress -pl wicket-migration -am clean verify
  • JDK 25: mvn -B --no-transfer-progress clean verify -Pjs-test
  • Full 33-module reactor passed
  • 3,069 JVM tests: 0 failures, 0 errors, 24 skips
  • 109 JavaScript tests: 0 failures, 0 skips
  • Maven Enforcer dependency convergence passed
  • Complete diff reviewed; only wicket-migration/pom.xml changes

Built and verified with JAIPilot:

  • Skills: jaipilot-maintainer-intent, jaipilot-fast-execution, and jaipilot-review-diff
  • Execution profile: gpt-5.6-sol · xhigh · fast

@dependabot
dependabot Bot deleted the branch apache:dependabot/maven/io.micrometer-micrometer-core-1.17.1 August 31, 2026 14:52
@dependabot dependabot Bot closed this Aug 31, 2026
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.

1 participant