generator-springboot icon indicating copy to clipboard operation
generator-springboot copied to clipboard

Update dependency yeoman-environment to v4

Open renovate[bot] opened this issue 2 years ago • 2 comments

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yeoman-environment (source) 3.19.3 -> 4.4.3 age adoption passing confidence

Release Notes

yeoman/environment (yeoman-environment)

v4.4.3

Compare Source

v4.4.2

Compare Source

v4.4.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/yeoman/environment/compare/v4.4.0...v4.4.1

v4.4.0

Compare Source

  • add callback function support for generator scheduling (#​521) 1c3ff69

v4.3.0

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.3

Compare Source

  • fix change event api usage c4c3ac6

v4.1.2

Compare Source

  • queue commit only if changed file is pending 2af3410

v4.1.1

Compare Source

  • fix findFeature api and type 29eb6b0

v4.1.0

Compare Source

v4.0.0

Compare Source

  • requireGenerator type adjust.

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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.

renovate[bot] avatar Oct 23 '23 03:10 renovate[bot]

⚠ 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 could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/yeoman-environment
npm ERR!   yeoman-environment@"4.4.0" from the root project
npm ERR!   peerOptional yeoman-environment@"^3.2.0" from [email protected]
npm ERR!   node_modules/yeoman-generator
npm ERR!     yeoman-generator@"5.10.0" from the root project
npm ERR!     peer yeoman-generator@"*" from [email protected]
npm ERR!     node_modules/yeoman-test
npm ERR!       dev yeoman-test@"6.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer yeoman-environment@"^3.3.0" from [email protected]
npm ERR! node_modules/yeoman-test
npm ERR!   dev yeoman-test@"6.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/yeoman-environment
npm ERR!   peer yeoman-environment@"^3.3.0" from [email protected]
npm ERR!   node_modules/yeoman-test
npm ERR!     dev yeoman-test@"6.3.0" 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-03-09T22_03_30_184Z-debug-0.log

renovate[bot] avatar Oct 23 '23 03:10 renovate[bot]

⚠️ 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 could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/yeoman-environment
npm ERR!   yeoman-environment@"4.4.3" from the root project
npm ERR!   peerOptional yeoman-environment@"^3.2.0" from [email protected]
npm ERR!   node_modules/yeoman-generator
npm ERR!     yeoman-generator@"5.10.0" from the root project
npm ERR!     peer yeoman-generator@"*" from [email protected]
npm ERR!     node_modules/yeoman-test
npm ERR!       dev yeoman-test@"6.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer yeoman-environment@"^3.3.0" from [email protected]
npm ERR! node_modules/yeoman-test
npm ERR!   dev yeoman-test@"6.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/yeoman-environment
npm ERR!   peer yeoman-environment@"^3.3.0" from [email protected]
npm ERR!   node_modules/yeoman-test
npm ERR!     dev yeoman-test@"6.3.0" 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-04-20T10_18_09_668Z-debug-0.log

renovate[bot] avatar Jun 03 '24 22:06 renovate[bot]

closing in favor of #233

rajadilipkolli avatar Apr 22 '25 02:04 rajadilipkolli

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

renovate[bot] avatar Apr 22 '25 02:04 renovate[bot]