generator-springboot
generator-springboot copied to clipboard
Update dependency yeoman-environment to v4
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| yeoman-environment (source) | 3.19.3 -> 4.4.3 |
Release Notes
yeoman/environment (yeoman-environment)
v4.4.3
- chore: accept @yeoman/transform v2
f36bdf2
v4.4.2
- chore: allow @yeoman/adapter v2.0.0
ad43a3a - update badge
adda673
v4.4.1
What's Changed
- Bump tar from 6.2.0 to 6.2.1 by @dependabot in https://github.com/yeoman/environment/pull/523
- Bump ejs from 3.1.9 to 3.1.10 by @dependabot in https://github.com/yeoman/environment/pull/527
- add bun support as a package manager by @kravetsone in https://github.com/yeoman/environment/pull/532
New Contributors
- @kravetsone made their first contribution in https://github.com/yeoman/environment/pull/532
Full Changelog: https://github.com/yeoman/environment/compare/v4.4.0...v4.4.1
v4.4.0
v4.3.0
v4.2.1
v4.2.0
- add option to customize namespaces (#511)
3e4b12f - allow to run generators using relative paths. (#507)
cd68282 - add an additional dependency to peer dependencies. (#506)
bfac25b
v4.1.3
- fix change event api usage
c4c3ac6
v4.1.2
- queue commit only if changed file is pending
2af3410
v4.1.1
- fix findFeature api and type
29eb6b0
v4.1.0
- feat: expose findFeature
9cc5518aa6c0d2 - chore: test adjusts
6a2cc4ee929644 - chore: dependencies updates
e04a88807a1d5e
v4.0.0
requireGeneratortype 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.
⚠ 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
⚠️ 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
closing in favor of #233
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.