Bump conf to ^13.1.0 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
conf	^5.0.0 -> ^13.1.0

---

Release Notes

sindresorhus/conf (conf)

v13.1.0

Compare Source

• Add rootSchema and ajvOptions options (#​196) 2819caa
• Add TypeScript overload for .delete() to fix dot-notation typing (#​197) 8fdcdd7

v13.0.1

Compare Source

• Fix validation being incorrectly run before schema change (#​194) 529e762

v13.0.0

Compare Source

Breaking

• Switch from JSON Schema draft-v7 to draft-2020-12
  • Please read about the breaking changes.

This is only a breaking change if you use the schema option.

v12.0.0

Compare Source

Breaking

• Require Node.js 18 aa12658

v11.0.2

Compare Source

• Fix types for .delete() to allow access by dot notation (#​182) 5b9a6e3

v11.0.1

Compare Source

• Fix paths in package.json's exports (#​172) 99732a0

v11.0.0

Compare Source

Breaking

• Require Node.js 14 cea3d68
• This package is now pure ESM. Please read this.
• The projectName option is now required unless you use the cwd option.
  • Previously, the package fetched the package name from the closest package.json, but this is no longer possible with ESM.
  • If you target Node.js 18 or later, it's quite easy to read package.json.
• The projectVersion option is now required if you use the migration option.
• Remove encryption migration 80e1ff0
  • Make sure to upgrade to v10 first if you upgrade from a version earlier than v5.

v10.2.0

Compare Source

• Add beforeEachMigration option (#​167) 06262ab

v10.1.2

Compare Source

• Fix types for the upcoming TS 4.7 (#​163) eb1da20

v10.1.1

Compare Source

• Fix the configFileMode option for TypeScript (#​159) 07d275b

v10.1.0

Compare Source

• Add configFileMode option (#​158) 8345d71

v10.0.3

Compare Source

• Upgrade some dependencies f19ee6b

v10.0.2

Compare Source

• Minor performance improvement (#​153) 1ea9b28

v10.0.1

Compare Source

• Fix issue with onDidChange not always being called (#​143) 3a53356

v10.0.0

Compare Source

Breaking

• Require Node.js 12 4fa57ef
• Upgrade from Ajv 7 to Ajv 8

v9.0.2

Compare Source

• Add ajv-formats when a schema is used (#​144) 094ac38

v9.0.1

Compare Source

• Fix .reset() to correctly handle falsy default values (#​141) 735225e

v9.0.0

Compare Source

• Make the clearInvalidConfig option false by default b291021
  A lot of people found the previous default surprising.

v8.0.0

Compare Source

Breaking

• Fix .clear() behavior (#​136) 259ba9b
  Previously, it would not reset the values back to the default ones specified in the defaults or schema option. It correctly does this now.
• Update ajv to version 7. This might affect user using the schema option.

v7.1.2

Compare Source

• Fix the .get() TypeScript return type (#​117) 526002e

v7.1.1

Compare Source

• Export Options TypeScript type 71477a7

v7.1.0

Compare Source

• Use atomically package instead of write-file-atomic (#​115) 6c624a0

v7.0.1

Compare Source

• Fix the package daa002c

v7.0.0

Compare Source

Breaking

• Require Node.js 10 e28b8d9

Improvements

• Move to TypeScript (#​104) 41b0c10
  This hopefully should result in better types.

v6.2.4

Compare Source

• Fix issue with package.json inference when using the cwd option (#​107) 3ef2da0

v6.2.3

Compare Source

• Work around EXDEV error (#​106) 64b386a

v6.2.2

Compare Source

v6.2.1

Compare Source

• Improve docs 3ec30d2 66b1058 7e6fcbe

v6.2.0

Compare Source

• Warning: The migrations option is buggy. Don't use it at this time.
• Add semver range capabilities into migrations (#​88) df3a256

v6.1.0

Compare Source

• Add .reset() method (#​87) 52ca0dd
• Add watch option (#​77) 8bd3352

v6.0.1

Compare Source

• Fix the TypeScript types (#​90) b5a4676
  The types were accidentally looser than intended.

v6.0.0

Compare Source

Breaking for TypeScript users

• Improve TypeScript typings (#​73) ef63b11 ff54952 93ace80
  The types were made much better, but it will probably break for some users. You can now properly define a strongly-typed store. Example.
  Note: There's no way to use a dot-path like config.get('foo.bar') with a typed store. We're looking into how to support that: https://github.com/sindresorhus/conf/issues/86

Enhancements

• Add support for migrations (#​83) 931ffce

Fixes

• Add temporary workaround for Conf being packaged in a Snap app 68bbb46

---

Configuration

📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, 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.

[mui-bot]

Deploy preview: https://deploy-preview-16792--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 85ad43e

[LukasTy]

@hasdfa correct me if I'm wrong, but conf is used at dev runtime, hence, to maintain the current declaration of engines.node, we have to limit the updates to before v12, where they increased min node version to 18? 🤔

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[hasdfa]

@LukasTy Yes, conf is used only in dev runtime, and in production it will be stripped.
I think we may stay with the current version to avoid any conflicts with Node.js versions, is that okay?

[LukasTy]

I think we may stay with the current version to avoid any conflicts with Node.js versions, is that okay?

WDYT about bumping to ^10 since v11 introduced ESM?
Or do you prefer specifically sticking with the current major for some reason? 🤔

[hasdfa]

Okay, I will make some updates on x-telemetry package again soon, so maybe will do that update in the same PR and we can close this

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[hasdfa]

Should be solved in #17008

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.