Skip to content
New issue

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

Update dependency cosmiconfig to v5.2.1 #204

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cosmiconfig 5.0.7 -> 5.2.1 age adoption passing confidence

Release Notes

cosmiconfig/cosmiconfig (cosmiconfig)

v5.2.1

Compare Source

  • Chore: Upgrade js-yaml to avoid npm audit warning.

v5.2.0

Compare Source

  • Added: packageProp values can be arrays of strings, to allow for property names that include periods. (This was possible before, but not documented or deliberately supported.)
  • Chore: Replaced the lodash.get dependency with a locally defined function.
  • Chore: Upgrade js-yaml to avoid npm audit warning.

v5.1.0

Compare Source

  • Added: packageProp values can include periods to describe paths to nested objects within package.json.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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.

Copy link
Author

renovate bot commented Dec 9, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

File name: yarn.lock
[03:36:42.187] INFO (153): Installing tool node@9.11.2...
[03:36:48.863] WARN (153): Npm error:
npm ERR! weird error 1
[03:36:49.565] ERROR (153): node-gyp update command failed
[03:36:49.566] FATAL (153): Install tool node failed in 7.3s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants