[dependabot]

Bumps io.github.ascopes:protobuf-maven-plugin from 5.1.10 to 5.1.11.

Release notes

Sourced from io.github.ascopes:protobuf-maven-plugin's releases.

v5.1.11

What's Changed

• GH-1059: Deduplicate source root registrations by @​alerosmile in ascopes/protobuf-maven-plugin#1060
• GH-1061: Fix glob matching for non-default file systems by @​alerosmile in ascopes/protobuf-maven-plugin#1062

New Contributors

• @​alerosmile made their first contribution in ascopes/protobuf-maven-plugin#1060

Full Changelog: ascopes/protobuf-maven-plugin@v5.1.10...v5.1.11

Commits

• a9030e7 [maven-release-plugin] prepare release v5.1.11
• bb13827 Merge pull request #1062 from alerosmile/fix-proto-filters
• 72aa0bf Fix glob matching for non-default file systems
• 53bba55 Merge pull request #1060 from alerosmile/deduplicate-source-registration
• c6a4b81 Deduplicate source root registrations
• e85ffcf Merge pull request #1058 from ascopes/dependabot/maven/main/maven-09b6b11d70
• 6faa5f7 Bump the maven group across 2 directories with 3 updates
• bbea542 Add todo for class loading optimisation
• a65f6d2 Change PluginConfigurator class to final
• 2d84b7e [maven-release-plugin] prepare for next development iteration
• See full diff 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]

This is an automated review by Codex GPT-5.6 Luna(Max).

Compatibility analysis

Dependency: io.github.ascopes:protobuf-maven-plugin, source 5.1.10, target 5.1.11. The carried-forward ROUND_1 verdict is SAFE. The complete published-release path reviewed is 5.1.10 -> 5.1.11; no published release lies between them. The persisted target-release inventory was reused: a9030e7 (prepare 5.1.11), bb13827/72aa0bf (non-default-filesystem glob matching), 53bba55/c6a4b81 (source-root deduplication), e85ffcf/6faa5f7 (Maven dependency/group updates), bbea542 (class-loading optimization TODO), a65f6d2 (final PluginConfigurator), and 2d84b7e (next development iteration); the functional release notes identify GH-1059 and GH-1061. No new compatibility research was performed in this CI-only round. The carried-forward evidence is SAFE for API/ABI, runtime, configuration, serialization/wire, persistence, clients, transitive dependencies, licenses, and extension/plugin SPI: the change is limited to build-time protobuf source generation, does not alter Druid public or runtime APIs or generated data contracts, introduces no Druid configuration or client behavior change, preserves the reviewed dependency and licensing surface, and changes no Druid extension/plugin SPI. No Druid-relevant CONCERN, INCOMPATIBLE, or UNRESOLVED evidence remains.

Druid impact

The PR changes only the plugin version in extensions-core/protobuf-extensions/pom.xml. It affects test protobuf source generation through generate-test; it does not change Druid production code, runtime APIs, schemas, serialization formats, or user-facing behavior. The protobuf extension module and its generated-test compilation completed successfully with version 5.1.11. No tracked production or test source changed.

Validation

The exact-head diff passed git diff --check. The persisted ROUND_1 validation covered target plugin resolution and protobuf generated-test source generation; the current exact-head attempt 4 executed the upgraded plugin and completed the protobuf extension module successfully. Maven dependency and license metadata remained aligned, with no transitive or licensing issue found. The full-workflow retry completed the unit, separated-test, coverage, Docker, static-check, and timeline jobs successfully. No source or test changes were required.

CI gate

At exact current head ed85256c7ea125b5ed8a84f196d0041f9fc64da7, the PR is OPEN, non-draft, MERGEABLE, and CLEAN. The authoritative complete statusCheckRollup is SUCCESS: all 27 CheckRuns are COMPLETED/SUCCESS, 0 StatusContexts are reported, and every reported item succeeded. The prior exact-head attempt had 24/27 SUCCESS, a Kafka fault-tolerance event timeout, a HighAvailability sys.segments empty-result assertion, and downstream skipped coverage. The user-authorized additional full-workflow retry RERUN_FULL_WORKFLOW|ADDITIONAL_1 ran as workflow 38645429964 attempt 4 and resolved the exact-head gate to 27/27 SUCCESS; no failed, skipped, pending, queued, in-progress, neutral, cancelled, or unknown result remains.

Automation actions

Automation changed no files, pushed no commit, and performed no bounded repair. It reran the full workflow 38645429964 as attempt 4 under the user-authorized additional retry scope, then verified the exact-head green rollup before this approval. No closure or merge was performed.

No merge was performed.