Bump io.opentelemetry.instrumentation:gradle-plugins from 2.19.0-alpha to 2.26.1-alpha#4652
Open
dependabot[bot] wants to merge 5 commits intomainfrom
Conversation
Bumps [io.opentelemetry.instrumentation:gradle-plugins](https://github.com/open-telemetry/opentelemetry-java-instrumentation) from 2.19.0-alpha to 2.26.1-alpha. - [Release notes](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md) - [Commits](https://github.com/open-telemetry/opentelemetry-java-instrumentation/commits) --- updated-dependencies: - dependency-name: io.opentelemetry.instrumentation:gradle-plugins dependency-version: 2.26.1-alpha dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
added
the
dependencies
dependabot
bot
requested review from
jeanbisutti and
rajkumar-rangaraj
as code owners
…centralizing META-INF duplicate policy Upgraded com.gradleup.shadow:shadow-gradle-plugin version to 9.3.2 to be in sync with io.opentelemetry.instrumentation:gradle-plugins:2.26.1-alpha.
…ns upgrade Shadow service-file merging was incomplete for isolated agent classes, so metric exporter providers were not discoverable from the inst service path during instrumentation tests. That caused Javaagent startup failures (otel.metrics.exporter=otlp “exporter not found”) and cascaded test failures across methods, micrometer, azure-functions, and applicationinsights-web modules. Update shadow conventions to merge service descriptors into both META-INF/services and inst/META-INF/services, restoring provider loading for the agent classloader and passing unit tests.
Use Shadow AppendingTransformer with an explicit newline separator and include duplicate spring.factories inputs so all Spring Boot auto-configuration entries are preserved and properly delimited during merge. This prevents malformed merged META-INF/spring.factories content that broke smoke test app startup (e.g., missing servlet web server auto-config).
…fat jars SpringCloudStream smoke was failing because META-INF/spring.factories entries were appended as plain text, causing auto-configuration keys to be effectively overwritten. Switch back to PropertiesFileTransformer merge behavior for spring.factories (with duplicate resources included), so Spring Cloud Stream binder auto-config is preserved. Validated by passing SpringCloudStream Java21 smoke and focused regression checks.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps io.opentelemetry.instrumentation:gradle-plugins from 2.19.0-alpha to 2.26.1-alpha.
Release notes
Sourced from io.opentelemetry.instrumentation:gradle-plugins's releases.
... (truncated)
Changelog
Sourced from io.opentelemetry.instrumentation:gradle-plugins's changelog.
... (truncated)
Commits
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)