Repository navigation
chore(deps): bump @fastify/otel from 0.20.1 to 0.21.1 - #1496
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@fastify/otel](https://github.com/fastify/otel) from 0.20.1 to 0.21.1. - [Release notes](https://github.com/fastify/otel/releases) - [Changelog](https://github.com/fastify/otel/blob/main/CHANGELOG.md) - [Commits](fastify/otel@v0.20.1...v0.21.1) --- updated-dependencies: - dependency-name: "@fastify/otel" dependency-version: 0.21.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Looks good — straightforward dependency version bump.
Reviewed: package.json/package-lock.json diff for @ fastify/otel ^0.20.1 → ^0.21.1, including the transitive @ opentelemetry/instrumentation bump and new nested packages (api-logs, import-in-the-middle, es-module-lexer). All entries resolve to the standard npm registry with matching integrity hashes; no application/source code was touched.
Extended reasoning...
Dependency-only change (package.json + package-lock.json) bumping @ fastify/otel and its transitive @ opentelemetry/instrumentation dependency, with no source code modified; no injection/auth/data-exposure surface is touched. The lockfile entries are internally consistent and point to the real npm registry. The one ruled-out concern (a documented upstream breaking change in 0.21.0 around instrumented/enabled OTEL context splitting) is release-note behavior for the library itself, not something visible or actionable in this lockfile-only diff, so it doesn't change the mechanical nature of this bump.
Coverage Report for CI Build 37937663499Coverage remained the same at 85.259%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
This branch has not been deployed
1 participant
Bumps @fastify/otel from 0.20.1 to 0.21.1.
Release notes
Sourced from @fastify/otel's releases.
Changelog
Sourced from @fastify/otel's changelog.
... (truncated)
Commits
77a0549chore(release): 0.21.10a11643fix: preserve the error description on the request span for 5xx (#191)fc7cd7dchore: bump@opentelemetry/contrib-test-utilsfrom 0.68.0 to 0.69.0 (#194)4aa6a9bchore: bump@opentelemetry/instrumentation-httpfrom 0.221.0 to 0.222.0 (#193)097b4fcchore: bump@opentelemetry/instrumentationfrom 0.221.0 to 0.222.0 in the dep...2f8d5eechore(release): 0.21.07c02d0afeat: allow disabling handler instrumentation2369ecfchore(.npmrc): add min-release-agecb2dd03chore: bump@opentelemetry/contrib-test-utilsfrom 0.67.0 to 0.68.0 (#187)e1f5c99chore: bump@opentelemetry/instrumentation-httpfrom 0.220.0 to 0.221.0 (#186)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)