storm-software / storm-stack

⚡The Storm Stack monorepo contains utility applications, tools, and various libraries to create modern and scalable web applications.
Apache License 2.0
3 stars 0 forks source link

chore(deps): Bump @opentelemetry/otlp-exporter-base from 0.46.0 to 0.51.1 #82

Open dependabot[bot] opened 3 months ago

dependabot[bot] commented 3 months ago

Bumps @opentelemetry/otlp-exporter-base from 0.46.0 to 0.51.1.

Release notes

Sourced from @​opentelemetry/otlp-exporter-base's releases.

Experimental v0.51.1

0.51.1

:bug: (Bug Fix)

  • fix(instrumentation): update import-in-the-middle to 1.7.4

Experimental v0.51.0

0.51.0

:boom: Breaking Change

  • feat(sdk-node)!: remove long deprecated methods in favor of constructor options #4606 @​pichlermarc
    • NodeSDK.configureTracerProvider(), please use constructor options instead
    • NodeSDK.configureMeterProvider(), please use constructor options instead
    • NodeSDK.configureLoggerProvider(), please use constructor options instead
    • NodeSDK.addResource(), please use constructor options instead
    • NodeSDK.detectResources(), this is not necessary anymore, resources are now auto-detected on NodeSDK.start() if the constructor option autoDetectResources is unset, undefined or true.
  • feat(instrumentation): add patch and unpatch diag log messages #4641
    • Instrumentations should not log patch and unpatch messages to diag channel.
  • feat!(instrumentation): remove moduleExports generic type from instrumentation registration #4598 @​blumamir
    • breaking for instrumentation authors that depend on
      • InstrumentationBase
      • InstrumentationNodeModuleDefinition
      • InstrumentationNodeModuleFile

:rocket: (Enhancement)

  • refactor(instrumentation-grpc): move to use SEMATTRS #4633
  • feat(otlp-transformer): consolidate scope/resource creation in transformer #4600
  • feat(sdk-logs): print message when attributes are dropped due to attribute count limit #4614 @​HyunnoH
  • feat(sdk-node): add usage for the detector ServiceInstanceIdDetectorSync. #4626 @​maryliag
    • The resource detector can be added to default resource detector list by adding the value serviceinstance to the list of resource detectors on the environment variable OTEL_NODE_RESOURCE_DETECTORS, e.g OTEL_NODE_RESOURCE_DETECTORS=env,host,os,serviceinstance
    • The value can be overwritten by
      • merging a resource containing the service.instance.id attribute
      • using another resource detector which writes service.instance.id

:bug: (Bug Fix)

Experimental v0.50.0

0.50.0

:boom: Breaking Change

  • fix(exporter-*-otlp-grpc)!: lazy load gRPC to improve compatibility with @opentelemetry/instrumenation-grpc #4432 @​pichlermarc
    • Fixes a bug where requiring the gRPC exporter before enabling the instrumentation from @opentelemetry/instrumentation-grpc would lead to missing telemetry

... (truncated)

Commits
  • 41c2626 Merge pull request #4682 from dynatrace-oss-contrib/release/1.24.x-0.51.x-2
  • 7cb72a6 chore: prepare release 1.24.1/0.51.1
  • 8a6d03f chore: sync package-lock.json, adapt changelog
  • dfc883c fix(exporter-metrics-otlp-grpc) Add explicit otlp-exporter-base depen… (#4678)
  • 75817d7 fix(deps): update dependency import-in-the-middle to v1.7.4 (#4667)
  • fe132d7 fix(core): align inconsistent behavior of getEnv() and getEnvWithoutDefaults(...
  • 307e33a fix(resources): prevent circular import (resource -> detector -> resource -> ...
  • 3ab4f76 chore: prepare release 1.24.0/0.51.0 (#4650)
  • 31eb60d feat!(instrumentation): add patch and unpatch diag log messages (#4641)
  • 99431df feat!(instrumentation): remove moduleExports generic type from instrumentatio...
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

github-actions[bot] commented 3 months ago

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

socket-security[bot] commented 3 months ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/buffer@6.0.3 None +2 108 kB feross
npm/md5@2.3.0 None +3 34.9 kB pvorb
npm/prompts@2.4.2 None +2 203 kB terkelg
npm/react@18.2.0 environment +2 337 kB gnoff
npm/semver@7.5.4 None +2 124 kB npm-cli-ops
npm/toposort@2.0.2 None 0 16.7 kB marcelklehr
npm/tslib@2.6.2 None 0 84 kB typescript-bot

🚮 Removed packages: npm/@opentelemetry/otlp-exporter-base@0.46.0, npm/@opentelemetry/resources@1.19.0, npm/@opentelemetry/sdk-trace-node@1.19.0, npm/@opentelemetry/semantic-conventions@1.19.0, npm/@storm-software/config-tools@1.28.2, npm/@storm-software/config@1.3.5, npm/@storm-software/git-tools@2.1.6, npm/@storm-software/linting-tools@1.39.3, npm/@storm-software/testing-tools@1.34.1, npm/@storm-software/workspace-tools@1.60.20, npm/@swc-node/register@1.8.0, npm/@swc/cli@0.1.65, npm/@swc/core@1.3.107, npm/@swc/helpers@0.5.6, npm/@tamagui/animations-react-native@1.89.19, npm/@tamagui/build@1.79.17, npm/@tamagui/fake-react-native@1.89.11, npm/@tamagui/font-inter@1.79.17, npm/@tamagui/react-native-media-driver@1.89.20, npm/@tamagui/shorthands@1.89.20, npm/@tamagui/theme-builder@1.90.6, npm/@tamagui/themes@1.79.17, npm/@tamagui/toast@1.89.8, npm/@tamagui/web@1.90.6, npm/@tanstack/react-table@8.11.8, npm/@tanstack/table-core@8.11.8, npm/@testing-library/react@14.0.0, npm/@tokens-studio/sd-transforms@0.14.2, npm/@types/figlet@1.5.8, npm/@types/fs-extra@11.0.4, npm/@types/jest@29.5.12, npm/@types/md5@2.3.5, npm/@types/mdx@2.0.11, npm/@types/node@20.11.20, npm/@types/react-dom@18.2.19, npm/@types/react@18.2.55, npm/@types/react@18.2.57, npm/@types/semver@7.5.6, npm/@types/toposort@2.0.7, npm/@vercel/edge-config@0.4.1, npm/@vercel/otel@0.3.0

View full report↗︎

socket-security[bot] commented 3 months ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSource
Install scripts npm/esbuild@0.19.9
  • orphan: npm/esbuild@0.19.9

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/esbuild@0.19.9