Bump node-fetch from 2.6.1 to 3.1.1 in /script#23506
Conversation
Bumps [node-fetch](https://github.com/node-fetch/node-fetch) from 2.6.1 to 3.1.1. - [Release notes](https://github.com/node-fetch/node-fetch/releases) - [Changelog](https://github.com/node-fetch/node-fetch/blob/main/docs/CHANGELOG.md) - [Commits](node-fetch/node-fetch@v2.6.1...v3.1.1) --- updated-dependencies: - dependency-name: node-fetch dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Short summary: This PR broke a part of Nightly CI. Needs to be imported differently here, or downgraded to v2.x instead of v3.x. No known security impact to downgrading to latest v2.x, since it is just as patched for security as v3.x. is. I think this broke the "Bump dependencies" job/task, which runs only on the Nightly CI pipeline. (See: First Nightly run after this PR was merged has an error failing to import the node-fetch module: Failing CI run. All the Nightly runs since then have this same error.) node-fetch 2.x to 3.x is a breaking change, particularly with the module switching to ESM (standard ECMAScript JS module) instead of being CommonJS (Node-style module). It is recommended to stay on node-fetch 2.x unless we are consuming it from ESM. I don't think atom's build scripts are ESM, rather I think they are CommonJS.
Note that node-fetch v2 is as patched for security as node-fetch v3, as far as I can tell from broswing the project's releases. The latest security release of v2.x and v3.x were on the same day for apparently the same vulnerability. Edit to add: For what it's worth, I think the copy of node-fetch bumped by this PR is exclusively used here: https://github.com/atom/atom/blob/v1.59.0/script/lib/update-dependency/fetch-outdated-dependencies.js#L1 So the "correct thing to do" here consists only of correct use with regard to that one file used in the Nightly CI pipeline. |
This version has all the known security patches in v3.x, and is meanwhile the recommended version to use from CommonJS (NodeJS-style) modules, as opposed to ESM. Atom's build and CI scripts are all CommonJS as far as I know, so we should basically stay on node-fetch v2.x. This fixes the currently broken "Bump dependencies" job in Nightly CI. Effectively reverts ad1318e, AKA atom#23506, albeit with a more up-to-date patch version of node-fetch v2.x.
|
Thanks for catching this 🙇🏾 @DeeDeeG |
Bumps node-fetch from 2.6.1 to 3.1.1.
Release notes
Sourced from node-fetch's releases.
... (truncated)
Changelog
Sourced from node-fetch's changelog.
... (truncated)
Commits
36e47e83.1.1 release (#1451)5304f3fDon't change relative location header on manual redirect (#1105)f5d3cf5fix(Headers): don't forward secure headers to 3th party (#1449)f2c3d56Create SECURITY.md (#1445)4ae3538core: Warn when using data (#1421)41f53b9fix: use more node: protocol imports (#1428)f674875ci: fix main branch (#1429)1493d04core: Don't use global buffer (#1422)eb33090Chore: Fix logical operator priority (regression) to disallow GET/HEAD with n...7ba5bc9update readme for TS@type/node-fetch(#1405)Maintainer changes
This version was pushed to npm by endless, a new releaser for node-fetch since your current version.
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 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 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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.