build(deps): bump org.apache.maven.resolver:maven-resolver-impl from 1.3.1 to 2.0.21

[dependabot]

Bumps org.apache.maven.resolver:maven-resolver-impl from 1.3.1 to 2.0.21.

Release notes

Sourced from org.apache.maven.resolver:maven-resolver-impl's releases.

2.0.21

🚀 New features and improvements

• RRF: self-heal from provably broken auto-discovered prefixes files (#1976) @​ascheman
• Feat: config to close connection at end of tx (#1978) @​cstamas
• Feat: new (limited) transport (#1966) @​cstamas
• Expose additional transport details to TransportListener (#1762) @​kwin
• Support HTTP/3 in Jetty and JRE HTTP Client (#1949) @​kwin
• Skip validation and decoration on re-entrant RepositorySystem calls (#1957) @​gnodet

🐛 Bug Fixes

• Fix: preserve original trace data when stamping re-entrancy marker (#1980) @​gnodet
• Bug: in certain cases Resolver caused build failure (#1975) @​cstamas
• Make sure to always close input streams bound to responses (#1970) @​kwin
• Fix: be more defensive regarding request traces (#1973) @​cstamas
• Fix reporting of HTTP/3 in JdkTransporter (#1967) @​kwin
• Validate path components (#1959) @​cstamas
• Bug: Apache transport deadlock in concurrent use case (#1953) @​cstamas
• Fix potential NPEs in IpcClient and resource leak in DependencyGraphParser (#1945) @​gnodet
• Bug: Jetty transport used wrong config (#1948) @​cstamas

📝 Documentation updates

• fix: Some since javadoc tags were off; fixed (#1968) @​cstamas
• Add AGENTS.md + SECURITY.md security-model pointer for scanner discoverability (#1950) @​potiuk

👻 Maintenance

• Use try-with-resources in AbstractTransporter (#1947) @​Aayush10016
• Add AGENTS.md + SECURITY.md security-model pointer for scanner discoverability (#1950) @​potiuk
• Fix potential NPEs in IpcClient and resource leak in DependencyGraphParser (#1945) @​gnodet
• Limit internal retries to 1 with Java 26+ (#1946) @​kwin

🔧 Build

• Use custom doclet to extract configuration metadata with the help of (#1965) @​kwin

📦 Dependency updates

• Bump Jetty to 12.1.11 (#1969) @​cstamas
• Bump apache/maven-gh-actions-shared/.github/workflows/release-drafter.yml from 4 to 5 (#1963) @dependabot[bot]
• Bump apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml from 4 to 5 (#1961) @dependabot[bot]
• Bump apache/maven-gh-actions-shared/.github/workflows/stale.yml from 4 to 5 (#1960) @dependabot[bot]
• Bump apache/maven-gh-actions-shared/.github/workflows/pr-automation.yml from 4 to 5 (#1962) @dependabot[bot]
• Bump bouncycastleVersion from 1.84 to 1.85 (#1956) @dependabot[bot]

2.0.20

... (truncated)

Commits

• 838477a [maven-release-plugin] prepare release maven-resolver-2.0.21
• f598880 Add ATR meta (#1982)
• 1e5d22a Fix: preserve original trace data when stamping re-entrancy marker (#1980)
• f4d1fa9 RRF: self-heal from provably broken auto-discovered prefixes files (#1976)
• 8532889 Bug: in certain cases Resolver caused build failure (#1975)
• 0feb214 Feat: config to close connection at end of tx (#1978)
• f974235 Do not check UrlTransporter for open connections after close
• dbaf309 Make sure to always close input streams bound to responses (#1970)
• 45482a8 Fix: be more defensive regarding request traces (#1973)
• 4bb69ad Fix tools classpath
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[FrankChen021]

I verified this PR at head 0a917b9fcfc2e4b28560c4ae86bf16fb3c48de29 against master 8855072aab605c68a4705f7d69875673bfbf81d4. The only changed path is services/pom.xml, changing org.apache.maven.resolver:maven-resolver-impl from 1.3.1 to 2.0.21.

This head is not approvable. The exact-head unit-test logs, strict-compilation logs, packaging logs, web-check logs, and all three CodeQL language jobs fail compiling PullDependencies.java because org.eclipse.aether.impl.DefaultServiceLocator is missing. I independently reproduced the same two-symbol compile failure with JDK 25 in the assigned worktree.

The effective dependency tree also fails Maven Enforcer: maven-resolver-impl:2.0.21 requests API/SPI/Util 2.0.21, while Druid directly pins those modules, the connector, and HTTP transport to 1.3.1; maven-resolver-provider:3.6.0 also brings Resolver 1.3.1. The Resolver project documents that clients must align API, SPI, Util, impl, connectors, and transports to one version (compatibility contract), and its 1.x-to-2.x guide requires session-lifecycle migration (upgrade guide). The 2.0.21 artifact does not contain DefaultServiceLocator, and the current 2.x transport family is different from Druid's maven-resolver-transport-http declaration (2.0.21 dependency inventory).

Fixing this is therefore not a safe one-line version bump: it requires a coordinated Resolver-family/provider/transport migration, production and test source changes around DefaultServiceLocator and session handling, server dependency alignment, license metadata updates, and focused regression coverage for pull-deps. The branch is also reported as not maintainer-writable (maintainerCanModify=false), so I cannot apply a surgical fix here. Closing this PR as CLOSED_HIGH_EFFORT; please reopen with a coordinated migration PR if the 2.x upgrade is still desired.

[FrankChen021]

Closed after the verified high-effort compatibility and build review documented in the preceding comment.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.