-
Notifications
You must be signed in to change notification settings - Fork 42
chore(deps-dev): bump node-fetch from 2.7.0 to 3.3.2 in /packages/instrumentation-openai #667
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 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
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 2ce487b in 1 minute and 11 seconds. Click for details.
- Reviewed
13
lines of code in1
files - Skipped
0
files when reviewing. - Skipped posting
1
draft 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-openai/package.json:59
- Draft comment:
Bumped node-fetch to v3.3.2 which is now ESM‑only and includes built-in type definitions. Ensure that any imports (especially in tests or tooling) use ESM syntax. Also, consider removing the '@types/node-fetch' dependency to avoid potential type conflicts. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." This is exactly what this comment is about - a dependency version change and its implications. Even though the comment is technically correct about the ESM changes, it's not the kind of comment we should keep. The comment does point out a potentially important breaking change in the dependency that could cause runtime issues. Maybe this is important enough to warrant keeping? No - the rules are very clear about not commenting on dependency changes. If there are runtime issues, they will be caught by the build and tests. Delete this comment as it violates our rule about not commenting on dependency changes and versions.
Workflow ID: wflow_pVXgvOMPix47Drs1
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
Bumps [node-fetch](https://github.com/node-fetch/node-fetch) from 2.7.0 to 3.3.2. - [Release notes](https://github.com/node-fetch/node-fetch/releases) - [Commits](node-fetch/node-fetch@v2.7.0...v3.3.2) --- updated-dependencies: - dependency-name: node-fetch dependency-version: 3.3.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
2ce487b
to
64e4ad9
Compare
Bumps node-fetch from 2.7.0 to 3.3.2.
Release notes
Sourced from node-fetch's releases.
... (truncated)
Commits
8b3320d
fix: Remove the default connection close header. (#1736)7b86e94
fix: release "Allow URL class object as an argument for fetch()" #1696 (#1716)8ced5b9
docs: readme - non ESM example (#1707)71e376b
ci(release): use latest Node LTS (#1697)e093030
Allow URL class object as an argument for fetch() (#1696)55a4870
feat: add static Response.json (#1670)c071406
(1138) - Fixed HTTPResponseError with correct constructor and usage (#1666)6f72caa
docs: fix missing comma in example (#1623)2880238
fix: ReDoS referrer (#1611)e87b093
fix(Headers): don't forward secure headers on protocol change (#1599)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 <dependency name> 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)Important
Bump
node-fetch
from 2.7.0 to 3.3.2 ininstrumentation-openai
package'spackage.json
.node-fetch
from 2.7.0 to 3.3.2 inpackage.json
forinstrumentation-openai
package.This description was created by
for 2ce487b. You can customize this summary. It will automatically update as commits are pushed.