Skip to content

chore(got): update dependency got to v14#67

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/got-14.x
Open

chore(got): update dependency got to v14#67
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/got-14.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 30, 2023

This PR contains the following updates:

Package Change Age Confidence
got ^13^14.0.0 age confidence

Release Notes

sindresorhus/got (got)

v14.6.6

Compare Source

  • Fix stream auto-end for empty PATCH/DELETE/OPTIONS 4d5168c
    • The bug was introduced in b65b0e1, where it incorrectly auto-closed streams for empty PATCH/DELETE/OPTIONS when using streams. This broke the documented use case of piping data to a got stream for these methods.
    • Docs:

      got.stream does not auto-end for OPTIONS, DELETE, or PATCH so you can pipe or write a body without getting write after end. Call stream.end() when you are not piping a body.


v14.6.5

Compare Source

  • Fix TypeScript type inference for got.extend() with responseType option f7ab6e9

v14.6.4

Compare Source

  • Fix dnsLookup option type to accept Node.js dns.lookup 47c3155

v14.6.3

Compare Source


v14.6.2

Compare Source

  • Fix path segments containing colons being misidentified as absolute URLs 0a16a9c

v14.6.1

Compare Source

  • Fix the TS code not being built in 14.6.0.

v14.6.0

Compare Source

Improvements
Fixes
  • Fix HTTP/2 timings NaN issue 398c11a
  • Fix shortcut methods ignoring handler errors f004564
  • Fix body reassignment in beforeRetry hooks bf84d36
  • Fix beforeError hook not being called for ERR_UNSUPPORTED_PROTOCOL error fb86418
  • FIx preserving prefixUrl in hooks 9725fbd
  • Fix race condition causing retry after promise settles 1e49781
  • Fix stream validation errors causing unhandled rejections 2527bf6
  • Fix incorrect content-length when piping decompressed responses 30b3b79
  • Fix EPIPE errors bypassing retry logic in Promise API 6ae3e7f
  • Fix silent hang when returning cached response with FormData body from beforeRequest hook e09a9bd
  • Fix hook type definitions to reflect normalized runtime state 6a544a3
  • Fix afterResponse hook validation to allow null body values 60a4419
  • Fix DNS timing being non-zero when connecting to IP addresses 3d66aec
  • Fix timings.end being undefined when stream is destroyed before completion 4e75679
  • Fix properly treating different UNIX socket paths as different origins e5659d4
Meta

I managed to get it almost down to zero issues! 🎉


v14.5.0

Compare Source

  • Add retry.enforceRetryRules option to fix statusCodes/limit bypassing 7c0aee6
  • Add support for serverName HTTPS option cdaab63
  • Add preserveHooks option for retryWithMergedOptions 1abeba4
  • Support Iterable and AsyncIterable as request body b65b0e1
  • Fix hang on revalidated cached responses 2ab94fd
  • Fix handling of FormData getLength errors a2812de
  • Fix downloadProgress firing for redirect responses 9ec6ff0
  • Fix TypeScript type definition for retry event's createRetryStream parameter e899c07
  • Fix validation to accept false as agent value 6961284
  • Fix HTTP/2 memory leak from timeout listeners with connection reuse d1d4ed2
  • Fix QuickLRU v7+ compatibility 23d0b6b
  • Fix it not using HTTP/2 connection reuse by default 724d592
  • Fix hang with stream requests without body for methods like OPTIONS dc4f1e3

v14.4.9

Compare Source

  • Fix hang with responses containing content-encoding headers but no body cc434bc

v14.4.8

Compare Source

  • Fix infinite loop when retrying with request.options in afterResponse hook dad6a91

v14.4.7

Compare Source


v14.4.6

Compare Source

v14.4.5

Compare Source

v14.4.4

Compare Source

v14.4.3

Compare Source

v14.4.2

Compare Source

v14.4.1

Compare Source

v14.4.0

Compare Source

v14.3.0

Compare Source

v14.2.1

Compare Source

v14.2.0

Compare Source

  • Add cause property with the original error to RequestError (#​2327) 4cbd01d

v14.1.0

Compare Source

v14.0.0

Compare Source

Breaking
  • Require Node.js 20 (#​2313) a004263
    • Why not target the oldest active Node.js LTS, which is Node.js 18? I usually strictly follow this convention in my packages. However, this package is the exception because the HTTP part of Node.js is consistently buggy, and I don't have time to work around issues in older Node.js releases. I you need to still support Node.js 18, I suggest staying on Got v13, which is quite stable. Node.js 18 will be out of active LTS in 5 months.
Improvements

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: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from JaneJeon November 30, 2023 08:40
@renovate
Copy link
Contributor Author

renovate bot commented Nov 30, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: got-ssrf@2.0.1
npm ERR! Found: got@14.0.0
npm ERR! node_modules/got
npm ERR!   peer got@"^14.0.0" from @janejeon/got@0.2.0
npm ERR!   packages/got
npm ERR!     @janejeon/got@0.2.0
npm ERR!     node_modules/@janejeon/got
npm ERR!       workspace packages/got from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer got@"^12 || ^13" from got-ssrf@2.0.1
npm ERR! node_modules/got-ssrf
npm ERR!   peer got-ssrf@"^2" from @janejeon/got@0.2.0
npm ERR!   packages/got
npm ERR!     @janejeon/got@0.2.0
npm ERR!     node_modules/@janejeon/got
npm ERR!       workspace packages/got from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: got@13.0.0
npm ERR! node_modules/got
npm ERR!   peer got@"^12 || ^13" from got-ssrf@2.0.1
npm ERR!   node_modules/got-ssrf
npm ERR!     peer got-ssrf@"^2" from @janejeon/got@0.2.0
npm ERR!     packages/got
npm ERR!       @janejeon/got@0.2.0
npm ERR!       node_modules/@janejeon/got
npm ERR!         workspace packages/got from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/f5f5fe/39ac1c/cache/others/npm/_logs/2023-11-30T08_40_46_146Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/f5f5fe/39ac1c/cache/others/npm/_logs/2023-11-30T08_40_46_146Z-debug-0.log

@renovate renovate bot force-pushed the renovate/got-14.x branch from a1a1725 to 95c09d6 Compare August 10, 2025 14:08
@renovate
Copy link
Contributor Author

renovate bot commented Aug 10, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: got-ssrf@2.0.1
npm error Found: got@14.6.6
npm error node_modules/got
npm error   peer got@"^14.0.0" from @janejeon/got@0.2.1
npm error   packages/got
npm error     @janejeon/got@0.2.1
npm error     node_modules/@janejeon/got
npm error       workspace packages/got from the root project
npm error
npm error Could not resolve dependency:
npm error peer got@"^12 || ^13" from got-ssrf@2.0.1
npm error node_modules/got-ssrf
npm error   peer got-ssrf@"^2" from @janejeon/got@0.2.1
npm error   packages/got
npm error     @janejeon/got@0.2.1
npm error     node_modules/@janejeon/got
npm error       workspace packages/got from the root project
npm error
npm error Conflicting peer dependency: got@13.0.0
npm error node_modules/got
npm error   peer got@"^12 || ^13" from got-ssrf@2.0.1
npm error   node_modules/got-ssrf
npm error     peer got-ssrf@"^2" from @janejeon/got@0.2.1
npm error     packages/got
npm error       @janejeon/got@0.2.1
npm error       node_modules/@janejeon/got
npm error         workspace packages/got from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-12T13_30_09_783Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-12T13_30_09_783Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants