graphql-config
graphql-config copied to clipboard
fix(deps): update dependency cosmiconfig to v9
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| cosmiconfig | ^8.1.0 -> ^9.0.0 |
Release Notes
cosmiconfig/cosmiconfig (cosmiconfig)
v9.0.0
- Added
searchStrategyoption:- The
nonevalue means that cosmiconfig does not traverse any directories upwards.- Breaking change: This is the default value if you don't pass a
stopDiroption, which means that cosmiconfig no longer traverses directories by default, and instead just looks in the current working directory.- If you want to achieve maximum backwards compatibility without adding an explicit
stopDir, add thesearchStrategy: 'global'option.
- If you want to achieve maximum backwards compatibility without adding an explicit
- Breaking change: This is the default value if you don't pass a
- The
projectvalue means that cosmiconfig traverses upwards until it finds apackage.json(or.yaml) file. - The
globalvalue means that cosmiconfig traverses upwards until the passedstopDir, or your home directory if nostopDiris given.
- The
- Breaking change: Meta config files (i.e.
config.jsand similar) are not looked for in the current working directory anymore. Instead, it looks in the.configsubfolder. - Breaking change: When defining
searchPlacesin a meta config file, the tool-definedsearchPlacesare merged into this. Users may specifymergeSearchPlaces: falseto disable this. - Added support for a special
$importkey which will import another configuration file- The imported file will act as a base file - all properties from that file will be applied to the configuration, but can be overridden by the importing file
- For more information, read the import section of the README
- Added searching in OS conventional folders (XDG compatible on Linux, %APPDATA% on Windows, Library/Preferences on macOS) for
searchStrategy: 'global' - Fixed crash when trying to load a file that is not readable due to file system permissions
- Fixed wrong ERR_REQUIRE_ESM error being thrown when there is an issue loading an ESM file
Configuration
📅 Schedule: Branch creation - "after 10pm,before 6:00am" in timezone Europe/Warsaw, 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.
💻 Website Preview
The latest changes are available as preview in: https://6ef27722.graphql-config.pages.dev
🚀 Snapshot Release (alpha)
The latest changes of this PR are available as alpha on npm (based on the declared changesets):
| Package | Version | Info |
|---|---|---|
graphql-config |
5.1.4-alpha-20250211023213-1b5710e707bb0969f9f7f058ca4550780fd45187 |
npm ↗︎ unpkg ↗︎ |
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.