opentelemetry-dotnet-instrumentation
opentelemetry-dotnet-instrumentation copied to clipboard
open-telemetry
Bump Microsoft.Extensions.Logging.Abstractions from 6.0.0 to 6.0.2 in /src/OpenTelemetry.AutoInstrumentation.AdditionalDeps
Bumps Microsoft.Extensions.Logging.Abstractions from 6.0.0 to 6.0.2.
Release notes
Sourced from Microsoft.Extensions.Logging.Abstractions's releases.
.NET 6.0.2
.NET 6.0.1
Commits
839cdfbMerge in 'release/6.0' changes6de5c5b[wasm][debugger] Missing test files (#63148)71075a0Merge in 'release/6.0' changes3c2d2a1Fix the MacOS remote unwinder for VS4Mac (#63405)d8f7045Merge in 'release/6.0' changesfe7335c[release/6.0] Use "read" to fetch misaligned 64bit values from bundle header ...5e9fd16Merge in 'release/6.0' changesbeedfae[release/6.0] Build all packages when in source-build (#63653)56c11f2Merge in 'release/6.0' changes27eb94bMerge in 'release/6.0' changes- 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@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)
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
@rajkumar-rangaraj I'm leaning towards closing this PR and perhaps marking it as ignored in the dependabot config. However, since we package this dependency as a fallback, should we ensure that we use the latest patch release? I'm not sure if doing that will lead to other dependency resolution issues.
@nrcventura Yes, we could close this PR.
It's recommended to maintain the latest version of the packages in OpenTelemetry.AutoInstrumentation.AdditionalDeps to avoid dependency resolution issues.
It's recommended to maintain the latest version of the packages in
OpenTelemetry.AutoInstrumentation.AdditionalDepsto avoid dependency resolution issues.
If that's the case, and it won't cause dependency resolution problems, perhaps we need to update the *.verified files and merge this PR?
To keep it clean, we could close this dependabot PR and create a new PR with all changes.
After this bump we get two (sic!) versions of Microsoft.Extensions.Logging.Abstractions: 6.0.0 and 6.0.2 under \store. Does anyone have an idea why (I have not made any deep analysis)?
Duplicated libraries are removed based on list. Build should fail if the dependency will be no available or it will be referenced from json file. Output structure tests should cover verification phase for manual modifications.
It is ugly, but in my opinion it is better than overriding msbuild steps.