-
Notifications
You must be signed in to change notification settings - Fork 46
chore(deps): bump @opentelemetry/instrumentation from 0.203.0 to 0.207.0 in /packages/instrumentation-langchain #809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed everything up to dca697b in 49 seconds. Click for details.
- Reviewed
13lines of code in1files - Skipped
0files when reviewing. - Skipped posting
1draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. packages/instrumentation-langchain/package.json:44
- Draft comment:
The dependency version bump to ^0.207.0 includes some breaking changes (e.g., Jaeger exporter lazy-loading removal). Please verify that this change does not adversely affect the instrumentation logic, and double-check that related functionality (exporters or context-handling) is still working as expected. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is related to a dependency version change and asks the PR author to verify and double-check the impact of the change. According to the rules, comments should not ask the author to confirm or double-check things, especially related to dependencies. Therefore, this comment should be removed.
Workflow ID: wflow_iqs5HbRUvmsSyeNX
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
87d021f to
15e4b5b
Compare
15e4b5b to
a243f42
Compare
a243f42 to
2a9570f
Compare
Bumps [@opentelemetry/instrumentation](https://github.com/open-telemetry/opentelemetry-js) from 0.203.0 to 0.207.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-js@experimental/v0.203.0...experimental/v0.207.0) --- updated-dependencies: - dependency-name: "@opentelemetry/instrumentation" dependency-version: 0.207.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2a9570f to
2f60a1e
Compare
Bumps @opentelemetry/instrumentation from 0.203.0 to 0.207.0.
Release notes
Sourced from
@opentelemetry/instrumentation's releases.... (truncated)
Commits
fb6476dchore: prepare next release (#6008)2d115fdtest: test Node.js 25 in CI (#6019)fe8fd65feat(opentelemetry-configuration): support file with format rc.2 (#6029)91e0d23chore(deps): update actions/setup-node action to v6 (#6028)3bb5717test(opentelemetry-configuration): ensureprocess.envis cleaned up after `...a93b1dcchore(move-to-emeriuts): create token before checkout (#6018)a39500dtest(otlp-grpc-exporter-base): remove duplicateddeletestatements (#6022)8c62fb1chore(deps): Updateimport-in-the-middle(#6020)6854413test(sdk-logs): ensure process.env is cleaned up between tests (#6017)3353b6ffeat(otlp-exporter-base): accept TLS config for node HTTP exporters from env ...Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@opentelemetry/instrumentationsince your current version.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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)Important
Bumps
@opentelemetry/instrumentationto 0.207.0, introducing breaking changes, new features, and bug fixes.@opentelemetry/instrumentationfrom 0.203.0 to 0.207.0 inpackage.json.OTEL_TRACE_EXPORTER=jaegerno longer instantiates Jaeger exporter.OTEL_TRACE_EXPORTER=otlpdue to Jaeger's native OTLP support.OTEL_EXPORTER_OTLP_CERTIFICATEand related env vars for OTLP HTTP exporters.batchLogProcessorexporting behavior and GRPC exporter user-agent header issue.This description was created by
for dca697b. You can customize this summary. It will automatically update as commits are pushed.