We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Undici@5 has a security issue described in GHSA-3787-6prv-h9w3
First non-vulnerable version is [email protected]. Unfortunately the security fix introduced Nullish coalescing operator which is not supported in Node.js@12.
This means that the undici patch release which is applied automatically with every swagger-client installation will break Node.js@12 compatibility.
We ideally want to break compatibility with Node@12 explicitly, when we need to.
Keeping security issue in production dep tree is not an option, which leaves us to remove undici@5 from our deps:
Fetch API support will move from this:
>=12.20.0 <16.8 - [node-fetch@3](https://www.npmjs.com/package/node-fetch) >=16.8 <18 - [undici](https://www.npmjs.com/package/undici) >=18 - [native Node.js fetch](https://nodejs.org/dist/latest-v18.x/docs/api/globals.html#fetch)
to the following
>=12.20.0 <18 - [node-fetch@3](https://www.npmjs.com/package/node-fetch) >=18 - [native Node.js fetch](https://nodejs.org/dist/latest-v18.x/docs/api/globals.html#fetch)
The text was updated successfully, but these errors were encountered:
fix(security): fix proxy-Authorization header security issue
4da0d89
Refs #3382
fix(security): fix proxy-Authorization header security issue (#3383)
649ab4b
Addressed by #3383
Sorry, something went wrong.
chore(release): cut the 3.25.2 release [skip ci]
900c2b5
## [3.25.2](v3.25.1...v3.25.2) (2024-02-22) ### Bug Fixes * **security:** fix proxy-Authorization header security issue ([#3383](#3383)) ([649ab4b](649ab4b)), closes [#3382](#3382)
char0n
No branches or pull requests
Undici@5 has a security issue described in GHSA-3787-6prv-h9w3
First non-vulnerable version is [email protected]. Unfortunately the security fix introduced Nullish coalescing operator which is not supported in Node.js@12.
This means that the undici patch release which is applied automatically with every swagger-client installation will break Node.js@12 compatibility.
We ideally want to break compatibility with Node@12 explicitly, when we need to.
Keeping security issue in production dep tree is not an option, which leaves us to remove undici@5 from our deps:
Fetch API support will move from this:
to the following
The text was updated successfully, but these errors were encountered: