Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2022

This PR contains the following updates:

Package Change Age Confidence
yaml-loader 0.6.0 -> 0.8.1 age confidence

Release Notes

eemeli/yaml-loader (yaml-loader)

v0.8.1

Compare Source

  • Fix namespace query handling (#​57)

v0.8.0

Compare Source

Breaking Changes
  • Require Node.js 12.13 or later
Other Changes
  • Improve error for missing asStream option

v0.7.0

Compare Source

Breaking Changes
  • Output JavaScript source by default, rather than JSON (#​27)
  • With the update to yaml@2, some of its options change (#​44)
  • Require Node.js 10.14.2 or later (d9f769f)
Other Changes
  • Update dependencies

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 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.

@renovate renovate bot force-pushed the renovate/yaml-loader-0.x branch from 72d429b to 8f811c9 Compare January 11, 2023 10:24
@renovate renovate bot changed the title Update dependency yaml-loader to v0.8.0 chore(deps): update dependency yaml-loader to v0.8.0 Jan 11, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Jan 11, 2023

⚠ Artifact update problem

Renovate failed to update an artifact 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
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: jest@27.5.1
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.2.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^29.0.0" from ts-jest@29.1.2
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^29.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-02-22T02_20_35_145Z-debug-0.log

@renovate renovate bot force-pushed the renovate/yaml-loader-0.x branch from 8f811c9 to f8f38b4 Compare February 22, 2024 02:20
@renovate renovate bot changed the title chore(deps): update dependency yaml-loader to v0.8.0 chore(deps): update dependency yaml-loader to v0.8.1 Feb 22, 2024
@renovate renovate bot force-pushed the renovate/yaml-loader-0.x branch from f8f38b4 to 415e1cf Compare August 11, 2025 03:44
Copy link
Contributor Author

renovate bot commented Aug 11, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact 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
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: jest@27.5.1
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.2.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^29.0.0 || ^30.0.0" from ts-jest@29.4.4
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^29.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-09-26T03_58_32_203Z-debug-0.log

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