search

2lambda123 / garden-io-garden

Mozilla Public License 2.0
0 stars 0 forks source link

chore(deps): bump @opentelemetry/sdk-node from 0.47.0 to 0.54.2 #405

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps @opentelemetry/sdk-node from 0.47.0 to 0.54.2.

Release notes

Sourced from @​opentelemetry/sdk-node's releases.

experimental/v0.54.2

0.54.2

:bug: (Bug Fix)

experimental/v0.54.1

0.54.1

:bug: (Bug Fix)

experimental/v0.54.0

0.54.0

:boom: Breaking Change

  • feat(exporter--otlp-)!: rewrite exporter config logic for testability #4971 @​pichlermarc
    • (user-facing) getDefaultUrl was intended for internal use has been removed from all exporters
    • (user-facing) getUrlFromConfig was intended for internal use and has been removed from all exporters
    • (user-facing) hostname was intended for internal use and has been removed from all exporters
    • (user-facing) url was intended for internal use and has been removed from all exporters
    • (user-facing) timeoutMillis was intended for internal use and has been removed from all exporters
    • (user-facing) onInit was intended for internal use and has been removed from all exporters
  • feat(otlp-exporter-base)!: do not export functions that are intended for internal use #4971 @​pichlermarc
    • Drops the following functions and types that were intended for internal use from the package exports:
      • parseHeaders
      • appendResourcePathToUrl
      • appendResourcePathToUrlIfNeeded
      • configureExporterTimeout
      • invalidTimeout
  • feat(instrumentation-http)!: remove long deprecated options #5085 @​pichlermarc
    • ignoreIncomingPaths has been removed, use the more versatile ignoreIncomingRequestHook instead.
    • ignoreOutgoingUrls has been removed, use the more versatile ignoreOutgoingRequestHook instead.
    • isIgnored utility function was intended for internal use and has been removed without replacement.

:rocket: (Enhancement)

  • feat(api-logs): Add delegating no-op logger provider #4861 @​hectorhdzg
  • feat(instrumentation-http): Add support for Semantic Conventions 1.27+ #4940 #4978 #5026 @​dyladan
    • Applies to client and server spans and metrics
    • Generate spans and metrics compliant with Semantic Conventions 1.27+ when OTEL_SEMCONV_STABILITY_OPT_IN contains http or http/dup
    • Generate spans and metrics backwards compatible with previous attributes when OTEL_SEMCONV_STABILITY_OPT_IN contains http/dup or DOES NOT contain http

:bug: (Bug Fix)

  • fix(sampler-jaeger-remote): fixes an issue where package could emit unhandled promise rejections @​Just-Sieb
  • fix(otlp-grpc-exporter-base): default compression to 'none' if env vars OTEL_EXPORTER_OTLP_TRACES_COMPRESSION and OTEL_EXPORTER_OTLP_COMPRESSION are falsy @​sjvans

... (truncated)

Commits


Dependabot compatibility score

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 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)

Summary by Sourcery

Chores:

performance-testing-bot[bot] commented 1 week ago

Unable to locate .performanceTestingBot config file

sourcery-ai[bot] commented 1 week ago

Reviewer's Guide by Sourcery

This PR updates the @opentelemetry/sdk-node dependency from version 0.47.0 to 0.54.2. The update includes several breaking changes in the OTLP exporters configuration, HTTP instrumentation options, and brings improvements to HTTP semantic conventions support and bug fixes.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Update OpenTelemetry SDK Node dependency version
  • Bump @opentelemetry/sdk-node from 0.47.0 to 0.54.2
  • Update package-lock.json to reflect the new version
 core/package.json
package-lock.json
Breaking changes in the dependency update
  • Remove internal OTLP exporter configuration functions and properties
  • Remove deprecated HTTP instrumentation options (ignoreIncomingPaths and ignoreOutgoingUrls)
  • Add support for Semantic Conventions 1.27+ in HTTP instrumentation
  • Fix ESM files wrapping with absolute path
  • Fix handling of malformed forwarded headers
 core/package.json
Tips and commands #### Interacting with Sourcery - **Trigger a new review:** Comment `@sourcery-ai review` on the pull request. - **Continue discussions:** Reply directly to Sourcery's review comments. - **Generate a GitHub issue from a review comment:** Ask Sourcery to create an issue from a review comment by replying to it. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a title at any time. - **Generate a pull request summary:** Write `@sourcery-ai summary` anywhere in the pull request body to generate a PR summary at any time. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) to: - Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others. - Change the review language. - Add, remove or edit custom review instructions. - Adjust other review settings. #### Getting Help - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).
korbit-ai[bot] commented 1 week ago

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

cr-gpt[bot] commented 1 week 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

code-companion-ai[bot] commented 1 week ago

Processing PR updates...

git-greetings[bot] commented 1 week ago

Thanks @dependabot[bot] for opening this PR!

For COLLABORATOR only :

coderabbitai[bot] commented 1 week ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
git-greetings[bot] commented 1 week ago
PR Details of @dependabot[bot] in garden-io-garden : OPEN CLOSED TOTAL
3 27 30