Update conf

package.json

@@ -43,13 +43,13 @@
 		"save"
 	],
 	"dependencies": {
-		"conf": "^12.0.0",
-		"type-fest": "^4.18.1"
+		"conf": "^13.0.0",
+		"type-fest": "^4.20.0"
 	},
 	"devDependencies": {
-		"ava": "^6.1.2",
-		"electron": "^30.0.1",
-		"execa": "^8.0.1",
+		"ava": "^6.1.3",
+		"electron": "^31.0.1",
+		"execa": "^9.2.0",
 		"tsd": "^0.31.0",
 		"xo": "^0.58.0"
 	},

readme.md

@@ -64,7 +64,7 @@ type: `object`
 
 [JSON Schema](https://json-schema.org) to validate your config data.
 
-Under the hood, the JSON Schema validator [ajv](https://github.com/epoberezkin/ajv) is used to validate your config. We use [JSON Schema draft-07](http://json-schema.org/latest/json-schema-validation.html) and support all [validation keywords](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md) and [formats](https://github.com/epoberezkin/ajv#formats).
+Under the hood, the JSON Schema validator [ajv](https://ajv.js.org/json-schema.html) is used to validate your config. We use [JSON Schema draft-2020-12](https://json-schema.org/draft/2020-12/release-notes) and support all validation keywords and formats.
 
 You should define your schema as an object where each key is the name of your data's property and each value is a JSON schema used to validate that property. See more [here](https://json-schema.org/understanding-json-schema/reference/object.html#properties).