[Snyk] Upgrade @opentelemetry/sdk-node from 0.44.0 to 0.53.0 #3
Conversation
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
Snyk has created this PR to upgrade @opentelemetry/sdk-node from 0.44.0 to 0.53.0. See this package in npm: @opentelemetry/sdk-node See this project in Snyk: https://app.snyk.io/org/gyenoch/project/ab60e8e9-a314-42ad-846f-f806bf8b9863?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Snyk has created this PR to upgrade @opentelemetry/sdk-node from 0.44.0 to 0.53.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 13 versions ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: @opentelemetry/sdk-node
-
0.53.0 - 2024-08-28
- fix(instrumentation)!:remove unused description property from interface #4847 @ blumamir
- feat(exporter--otlp-)!: use transport interface in node.js exporters #4743 @ pichlermarc
- (user-facing)
- (user-facing)
- (user-facing)
- fix(exporter--otlp-)!: ensure
- allowing overrides of the
- feat(exporter--otlp)!: remove environment-variable specific code from browser exporters
- (user-facing) removes the ability to configure browser exporters by using
- feat(sdk-node)!: Automatically configure logs exporter #4740
- feat(exporter--otlp-)!: use transport interface in browser exporters #4895 @ pichlermarc
- (user-facing) protected
- feat(otlp-transformer): Do not limit @ opentelemetry/api upper range peerDependency #4816 @ mydea
- feat(instrumentation-http): Allow to opt-out of instrumenting incoming/outgoing requests #4643 @ mydea
- feat(sampler-jaeger-remote): added support of jaeger-remote-sampler according to this spec #4534 @ legalimpurity
- fix(instrumentation): ensure .setConfig() results in config.enabled defaulting to true #4941 @ trentm
- fix(instrumentation-http): Ensure instrumentation of
- fix(api-logs): align AnyValue to spec #4893 @ blumamir
- fix(instrumentation): remove diag.debug() message for instrumentations that do not patch modules #4925 @ trentm
- refactor: Simplify the code for the
- refactor: remove "export *" in favor of explicit named exports #4880 @ robbkidd
- Packages updated:
- api-events
- api-logs
- opentelemetry-browser-detector
- opentelemetry-exporter-prometheus
- opentelemetry-instrumentation-fetch
- opentelemetry-instrumentation-http
- opentelemetry-instrumentation-xml-http-request
- opentelemetry-instrumentation
-
0.52.1 - 2024-06-20
- refactor(instrumentation-fetch): move fetch to use SEMATRR #4632
- refactor(otlp-transformer): use explicit exports #4785 @ pichlermarc
- fix(sdk-node): register context manager if no tracer options are provided #4781 @ pichlermarc
- fix(instrumentation): Update
- chore(instrumentation): Use a caret version for
- test: add
-
0.52.0 - 2024-06-05
- feat(exporter--otlp-)!: move serialization for Node.js exporters to
- Breaking changes:
- (user-facing)
- (internal) OTLPExporterNodeBase now has additional constructor parameters that are required
- (internal) OTLPExporterNodeBase now has an additional
- feat(exporter--otlp-)!: move serialization for Node.js exporters to
- Breaking changes:
- (user-facing)
- (internal) OTLPExporterBrowserBase:
- (internal) OTLPExporterNodeBase:
- (internal) the
- feat(instrumentation): remove default value for config in base instrumentation constructor #4695: @ blumamir
- fix(instrumentation)!: remove unused supportedVersions from Instrumentation interface #4694 @ blumamir
- feat(instrumentation)!: simplify
- Breaking changes:
- removes
- occurrences of
- migrate usages of
- passing Instrumentation classes to
- feat(sdk-node)!: simplify type of
- Breaking changes:
- replaces
- feat(instrumentation): apply unwrap before wrap in base class #4692
- feat(instrumentation): add util to execute span customization hook in base class #4663 @ blumamir
- feat(instrumentation): generic config type in instrumentation base #4659 @ blumamir
- feat: support node 22 #4666 @ dyladan
- feat(propagator-aws-xray-lambda): add AWS Xray Lambda propagator 4554
- refactor(instrumentation-xml-http-request): use exported strings for semantic attributes. #4681
- fix(instrumentation): Update
- docs(instrumentation): better docs for supportedVersions option #4693 @ blumamir
- docs: align all supported versions to a common format #4696 @ blumamir
- refactor(examples): use new exported string constants for semconv in experimental/examples/opencensus-shim #4763 @ Zen-cronic
-
0.51.1 - 2024-05-07
-
0.51.0 - 2024-04-24
-
0.50.0 - 2024-04-03
-
0.49.1 - 2024-02-29
-
0.49.0 - 2024-02-29
-
0.48.0 - 2024-01-26
-
0.47.0 - 2024-01-15
-
0.46.0 - 2023-12-14
-
0.45.1 - 2023-11-08
-
0.45.0 - 2023-11-07
-
0.44.0 - 2023-10-10
from @opentelemetry/sdk-node GitHub release notes0.53.0
💥 Breaking Change
headerswas intended for internal use has been removed from all exporterscompressionwas intended for internal use and has been removed from all exportershostnamewas intended for use in tests and is not used by any exporters, it will be removed in a future releaseUser-Agentheader cannot be overwritten by the user #4743 @ pichlermarcUser-Agentheader was not specification compliant.process.envpolyfillsheadersproperty was intended for internal use has been removed from all exporters🚀 (Enhancement)
🐛 (Bug Fix)
http.getandhttps.getwork when used in ESM code #4857 @ trentm🏠 (Internal)
getEnvfunction #4799 @ danstarns0.52.1
🚀 (Enhancement)
🐛 (Bug Fix)
import-in-the-middleto fix numerous bugs #4806 @ timfishimport-in-the-middledependency #4810 @ timfish🏠 (Internal)
npm run maint:regenerate-test-certsmaintenance script and regenerate recently expired test certs #47770.52.0
💥 Breaking Change
@ opentelemetry/otlp-transformer#4542 @ pichlermarcconvert()now returns an empty object and will be removed in a follow-upResponseTypetype parameter@ opentelemetry/otlp-transformer#4581 @ pichlermarcconvert()has been removed from all exportersRequestTypehas been replaced by aResponseTypetype-argumentServiceRequesthas been replaced by aServiceResponsetype-argument@ opentelemetry/otlp-exporter-proto-basepackage has been removed, and will from now on be deprecated innpmregisterInstrumentations()APIInstrumentationOptionstypeInstrumentationOptionsare now replaced by(Instrumentation | Instrumentation[])[]registerInstrumentations({instrumentations: fooInstrumentation})toregisterInstrumentations({instrumentations: [fooInstrumentation]})registerInstrumentations()is now not possible anymore.instrumentationsoptionInstrumentationOptionswith(Instrumentation | Instrumentation[])[]🚀 (Enhancement)
🐛 (Bug Fix)
import-in-the-middleto fix numerous bugs #4745 @ timfish📚 (Refine Doc)
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: