fix(deps): update dependency io.micrometer:micrometer-tracing-bom to v1.1.1 (main)

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.micrometer:micrometer-tracing-bom	1.0.4 -> 1.1.1

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

micrometer-metrics/tracing

v1.1.1: 1.1.1

Compare Source

This release fixes 1.1.0 mistakenly depending on the non-GA version 1.11.0-RC1 of the micrometer-bom.

🐞 Bug Fixes

• Dependency on micrometer-bom RC1 version in GA release #​255

v1.1.0: 1.1.0

Compare Source

Known issue: This release mistakenly depends on the non-GA version 1.11.0-RC1 of the micrometer-bom. This will be addressed in a forthcoming patch release. You should use that version instead. See https://github.com/micrometer-metrics/tracing/issues/255.

⭐ New Features / Enhancements

• Add ObservationAwareSpanThreadLocalAccessor constructor taking ObservationRegistry #​240
• Adds support for tags with typed values #​239
• Support numeric attributes value for tracing attributes #​234
• otel-bridge: add trace_flags to MDC #​229
• TracingObservationHandler doesn't include manually created spans #​244
• BaggageManager#getBaggage() is inconsistent when baggage doesn't exist #​237
• Aligning with annotations changes in Micrometer #​218
• Links API proposal #​204
• Feature parity with sleuth's annotations #​163
• Slf4JEventListener support custom key #​160
• Support custom MDC key with otel.bridge.Slf4JEventListener #​158
• No-op implementations for Propagator, Setter, and Getter #​118

📔 Documentation

• JavaDoc : Propagator references Open Telemetry classes which is not part of Micrometer #​230

🐞 Bug Fixes

• Different behaviour, hard to control between implementations #​184
• Reconsider the Baggage API #​181

🔨 Dependency Upgrades

• Remove opentelemetry-extension-aws #​245
• Upgrade OTel to 1.25 #​231
• Upgrade to Reactor 3.5.5 #​251
• Upgrade to Testcontainers 1.18.0 #​250
• Upgrade to JUnit 5.9.3 #​249
• Upgrade to Logback 1.2.12 #​248
• Upgrade Gradle to 8.1.1 #​246

❤️ Contributors

Thank you to all the contributors who worked on this release:

@​acktsap, @​ShenFeng312, and @​ttddyy

v1.0.6: 1.0.6

Compare Source

This release fixes 1.0.5 mistakenly depending on a previous version of the micrometer-bom (1.10.7 instead of 1.10.6).

🔨 Dependency Upgrades

• Upgrade to micrometer-bom 1.10.7 #​256

v1.0.5: 1.0.5

Compare Source

Known issue: This release mistakenly depends on a previous version of the micrometer-bom but it should have depend on the current one: 1.10.7 instead of 1.10.6. This will be addressed in a forthcoming patch release. You should use that version instead. See https://github.com/micrometer-metrics/tracing/issues/256.

🐞 Bug Fixes

• TracingObservationHandler doesn't include manually created spans #​244
• BaggageManager#getBaggage() is inconsistent when baggage doesn't exist #​237

📔 Documentation

• JavaDoc : Propagator references Open Telemetry classes which is not part of Micrometer #​230

🔨 Dependency Upgrades

• Upgrade to Reactor 3.5.5 #​251
• Upgrade to Testcontainers 1.18.0 #​250
• Upgrade to JUnit 5.9.3 #​249
• Upgrade to Logback 1.2.12 #​248
• Upgrade Gradle to 8.1.1 #​246

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green is not authorized to push to this branch. Visit https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions to give gcf-merge-on-green permission to push to this branch.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication