Pin io-ts version to v2.2.20

gcanti/io-ts#705 fixes an issue with io-ts and non-enumerable
properties, but that results in objects with invalid properties to get
removed during `decode`, which breaks our validation tests.

Need to figure out what is the right behavior for us

Change-type: patch
This commit is contained in:
Felipe Lalanne 2025-01-27 12:53:40 +00:00
parent 58824066e0
commit 88e821ed8e
No known key found for this signature in database
GPG Key ID: 03E696BFD472B26A
2 changed files with 3 additions and 2 deletions

3
package-lock.json generated
View File

@ -66,7 +66,7 @@
"fp-ts": "^2.16.5",
"got": "14.4.1",
"husky": "^9.1.7",
"io-ts": "^2.2.20",
"io-ts": "2.2.20",
"io-ts-reporters": "^2.0.1",
"json-mask": "^2.0.0",
"JSONStream": "^1.3.5",
@ -7615,6 +7615,7 @@
"resolved": "https://registry.npmjs.org/io-ts/-/io-ts-2.2.20.tgz",
"integrity": "sha512-Rq2BsYmtwS5vVttie4rqrOCIfHCS9TgpRLFpKQCM1wZBBRY9nWVGmEvm2FnDbSE2un1UE39DvFpTR5UL47YDcA==",
"dev": true,
"license": "MIT",
"peerDependencies": {
"fp-ts": "^2.5.0"
}

View File

@ -92,7 +92,7 @@
"fp-ts": "^2.16.5",
"got": "14.4.1",
"husky": "^9.1.7",
"io-ts": "^2.2.20",
"io-ts": "2.2.20",
"io-ts-reporters": "^2.0.1",
"json-mask": "^2.0.0",
"JSONStream": "^1.3.5",