octokit
fix(deps): update dependency node-fetch to v3
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| node-fetch | ^2.6.7 -> ^3.0.0 |
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.
This PR has been generated by Mend Renovate. View repository job log here.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
Just thought I'd say that without this dependency update, modern versions of node are emitting deprecation notices due to node-fetch 2.x's use of a whatwg-url from 2017 that uses new Buffer().
This PR is needed to fix https://github.com/actions/github-script/issues/202
That is not possible at this time. v3 of node-fetch switches to ESM, as discussed in previous comments, and the review comment.
Unfortunately the JS octokit libraries no longer have an active maintainer.
You can read about it in this discussion, subscribe to it for further updates.
That is not possible at this time.
v3ofnode-fetchswitches to ESM, as discussed in previous comments, and the review comment.Unfortunately the JS octokit libraries no longer have an active maintainer.
You can read about it in this discussion, subscribe to it for further updates.
Oh, such a shame they stopped support :(
Thanks