[Snyk] Upgrade: , , , , #195
Merged
Conversation
This file contains 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/instrumentation from 0.52.1 to 0.53.0.
See this package in npm: https://www.npmjs.com/package/@opentelemetry/instrumentation
- @opentelemetry/instrumentation-http from 0.52.1 to 0.53.0.
See this package in npm: https://www.npmjs.com/package/@opentelemetry/instrumentation-http
- @opentelemetry/resources from 1.25.1 to 1.26.0.
See this package in npm: https://www.npmjs.com/package/@opentelemetry/resources
- @opentelemetry/sdk-trace-base from 1.25.1 to 1.26.0.
See this package in npm: https://www.npmjs.com/package/@opentelemetry/sdk-trace-base
- @opentelemetry/sdk-trace-node from 1.25.1 to 1.26.0.
See this package in npm: https://www.npmjs.com/package/@opentelemetry/sdk-trace-node
See this project in Snyk:
https://app.snyk.io/org/saidsef-jq9/project/e4413c10-cd03-405c-bce3-d56caec15929?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 multiple dependencies.
👯♂ The following dependencies are linked and will therefore be updated together.ℹ️ 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.
@opentelemetry/instrumentation
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 21 days ago
on 2024-08-28
@opentelemetry/instrumentation-http
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 21 days ago
on 2024-08-28
@opentelemetry/resources
from 1.25.1 to 1.26.0 | 1 version ahead of your current version | 21 days ago
on 2024-08-28
@opentelemetry/sdk-trace-base
from 1.25.1 to 1.26.0 | 1 version ahead of your current version | 21 days ago
on 2024-08-28
@opentelemetry/sdk-trace-node
from 1.25.1 to 1.26.0 | 1 version ahead of your current version | 21 days ago
on 2024-08-28
Release notes
Package name: @opentelemetry/instrumentation
-
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
from @opentelemetry/instrumentation 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 #4777Package name: @opentelemetry/instrumentation-http
-
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
from @opentelemetry/instrumentation-http 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 #4777Package name: @opentelemetry/resources
-
1.26.0 - 2024-08-28
- feat: include instrumentation scope info in console span and log record exporters #4848 @ blumamir
- feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @ dyladan
- Exported names have changed to
- Import
- Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
- fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @ trentm
- deps(opentelemetry-instrumentation): Bump
- fix(instrumentation): Fix optional property types #4833 @ alecmev
- fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829
- refactor: Simplify the code for the
- refactor: remove "export *" in favor of explicit named exports #4880 @ robbkidd
- Packages updated:
- opentelemetry-context-zone
- opentelemetry-core
- opentelemetry-exporter-jaeger
- opentelemetry-exporter-zipkin
- opentelemetry-propagator-b3
- opentelemetry-propagator-jaeger
- opentelemetry-sdk-trace-base
- opentelemetry-sdk-trace-node
- opentelemetry-sdk-trace-web
- propagator-aws-xray
- sdk-metrics
- deps(sdk-metrics): remove unused lodash.merge dependency #4905 @ pichlermarc
-
1.25.1 - 2024-06-20
- refactor(examples): added usage of @ opentelemetry/semantic-conventions and @ opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @ Zen-cronic
- refactor(context-zone-peer-dep): use explicit exports #4785 @ pichlermarc
- refactor(context-async-hooks): use explicit exports #4785 @ pichlermarc
from @opentelemetry/resources GitHub release notes1.26.0
🚀 (Enhancement)
ATTR_{name}for attributes (e.g.ATTR_HTTP_REQUEST_METHOD),{name}_VALUE_{value}for enumeration values (e.g.HTTP_REQUEST_METHOD_VALUE_POST), andMETRIC_{name}for metrics. Exported names from previous versions are deprecated.@ opentelemetry/semantic-conventionsfor stable semantic conventions. Import@ opentelemetry/semantic-conventions/incubatingfor all semantic conventions, stable and unstable.🐛 (Bug Fix)
shimmertypes to 1.2.0 #4865 @ lforst🏠 (Internal)
getEnvfunction #4799 @ danstarns1.25.1
📚 (Refine Doc)
🏠 (Internal)
Package name: @opentelemetry/sdk-trace-base
-
1.26.0 - 2024-08-28
- feat: include instrumentation scope info in console span and log record exporters #4848 @ blumamir
- feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @ dyladan
- Exported names have changed to
- Import
- Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
- fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @ trentm
- deps(opentelemetry-instrumentation): Bump
- fix(instrumentation): Fix optional property types #4833 @ alecmev
- fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829
- refactor: Simplify the code for the
- refactor: remove "export *" in favor of explicit named exports #4880 @ robbkidd
- Packages updated:
- opentelemetry-context-zone
- opentelemetry-core
- opentelemetry-exporter-jaeger
- opentelemetry-exporter-zipkin
- opentelemetry-propagator-b3
- opentelemetry-propagator-jaeger
- opentelemetry-sdk-trace-base
- opentelemetry-sdk-trace-node
- opentelemetry-sdk-trace-web
- propagator-aws-xray
- sdk-metrics
- deps(sdk-metrics): remove unused lodash.merge dependency #4905 @ pichlermarc
-
1.25.1 - 2024-06-20
- refactor(examples): added usage of @ opentelemetry/semantic-conventions and @ opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @ Zen-cronic
- refactor(context-zone-peer-dep): use explicit exports #4785 @ pichlermarc
- refactor(context-async-hooks): use explicit exports #4785 @ pichlermarc
from @opentelemetry/sdk-trace-base GitHub release notes1.26.0
🚀 (Enhancement)
ATTR_{name}for attributes (e.g.ATTR_HTTP_REQUEST_METHOD),{name}_VALUE_{value}for enumeration values (e.g.HTTP_REQUEST_METHOD_VALUE_POST), andMETRIC_{name}for metrics. Exported names from previous versions are deprecated.@ opentelemetry/semantic-conventionsfor stable semantic conventions. Import@ opentelemetry/semantic-conventions/incubatingfor all semantic conventions, stable and unstable.🐛 (Bug Fix)
shimmertypes to 1.2.0 #4865 @ lforst🏠 (Internal)
getEnvfunction #4799 @ danstarns1.25.1
📚 (Refine Doc)
🏠 (Internal)
Package name: @opentelemetry/sdk-trace-node
-
1.26.0 - 2024-08-28
- feat: include instrumentation scope info in console span and log record exporters #4848 @ blumamir
- feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @ dyladan
- Exported names have changed to
- Import
- Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
- fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @ trentm
- deps(opentelemetry-instrumentation): Bump
- fix(instrumentation): Fix optional property types #4833 @ alecmev
- fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829
- refactor: Simplify the code for the
- refactor: remove "export *" in favor of explicit named exports #4880 @ robbkidd
- Packages updated:
- opentelemetry-context-zone
- opentelemetry-core
- opentelemetry-exporter-jaeger
- opentelemetry-exporter-zipkin
- opentelemetry-propagator-b3
- opentelemetry-propagator-jaeger
- opentelemetry-sdk-trace-base
- opentelemetry-sdk-trace-node
- opentelemetry-sdk-trace-web
- propagator-aws-xray
- sdk-metrics
- deps(sdk-metrics): remove unused lodash.merge dependency #4905 @ pichlermarc
-
1.25.1 - 2024-06-20
- refactor(examples): added usage of @ opentelemetry/semantic-conventions and @ opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @ Zen-cronic
- refactor(context-zone-peer-dep): use explicit exports #4785 @ pichlermarc
- refactor(context-async-hooks): use explicit exports #4785 @ pichlermarc
from @opentelemetry/sdk-trace-node GitHub release notes1.26.0
🚀 (Enhancement)
ATTR_{name}for attributes (e.g.ATTR_HTTP_REQUEST_METHOD),{name}_VALUE_{value}for enumeration values (e.g.HTTP_REQUEST_METHOD_VALUE_POST), andMETRIC_{name}for metrics. Exported names from previous versions are deprecated.@ opentelemetry/semantic-conventionsfor stable semantic conventions. Import@ opentelemetry/semantic-conventions/incubatingfor all semantic conventions, stable and unstable.🐛 (Bug Fix)
shimmertypes to 1.2.0 #4865 @ lforst🏠 (Internal)
getEnvfunction #4799 @ danstarns1.25.1
📚 (Refine Doc)
🏠 (Internal)
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: