Bump got from 11.8.2 to 12.1.0 in /packages/benchmarks/generator
Bumps got from 11.8.2 to 12.1.0.
Release notes
Sourced from got's releases.
v12.1.0
Improvements
- Add
response.ok(#2043) 22d58fb
- This is only useful if you have
{throwHttpErrors: false}Fixes
- Do not redirect to UNIX sockets (#2047) 861ccd9
https://github.com/sindresorhus/got/compare/v12.0.4...v12.1.0
v12.0.4
- Remove stream lock - unreliable since Node 17.3.0 bb8eca924c338ca12d5b90d6a26aa28dbddb42ee
v12.0.3
- Allow more types in the
jsonoption (#2015) eb045bfhttps://github.com/sindresorhus/got/compare/v12.0.2...v12.0.3
v12.0.2
- Fix
encodingoption with{responseType: 'json'}(#1996) 0703318https://github.com/sindresorhus/got/compare/v12.0.1...v12.0.2
v12.0.1
- Fix
nockcompatibility (#1959) bf39d2c- Fix missing export of
RequestTypeScript type (#1940) 0f9f2b8https://github.com/sindresorhus/got/compare/v12.0.0...v12.0.1
v12.0.0
Introducing Got v12.0.0 :tada:
Long time no see! The latest Got version (v11.8.2) was released just in February ❄️ We have been working hard on squashing bugs and improving overall experience.
If you find Got useful, you might want to sponsor the Got maintainers.
This package is now pure ESM
Please read this. Also see sindresorhus/got#1789.
- Please don't open issues about
[ERR_REQUIRE_ESM]andMust use import to load ES Moduleerrors. This is a problem with your setup, not Got.- Please don't open issues about using Got with Jest. Jest does not fully support ESM.
- Pretty much any problem with loading this package is a problem with your bundler, test framework, etc, not Got.
- If you use TypeScript, you will want to stay on Got v11 until TypeScript 4.6 is out. Why.
- If you use a bundler, make sure it supports ESM and that you have correctly configured it for ESM.
... (truncated)
Commits
ad92afa12.1.0861ccd9Disable redirects to UNIX sockets (#2047)4cdcca3Check error instance for arguments test (#2044)22d58fbAddresponse.ok(#2043)c25af09Meta tweaks62455f5Meta tweaks6f5c7ceTest Node.js 18c69342212.0.498ca618Fix accidental test deletionbb8eca9Remove stream lock - unreliable since Node 17.3.0- Additional commits viewable in compare view
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 language
You can disable automated security fix PRs for this repo from the Security Alerts page.
⚠️ No Changeset found
Latest commit: 364cf4c8c8630e5897cd31bb6efa7010f756c55d
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@dependabot rebase
Looks like got is up-to-date now, so this is no longer needed.