fix(deps): update dependency yeoman-environment to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
yeoman-environment (source)	3.19.3 -> 5.0.0

---

Release Notes

yeoman/environment (yeoman-environment)

v5.0.0

Compare Source

• chore(deps): bump locate-path from 7.2.0 to 8.0.0 (#​657) db2a7ce
• chore(deps): bump untildify from 5.0.0 to 6.0.0 (#​658) d63caf6
• chore: add @​yeoman/adapter to peerDependencies (#​656) ca2fa1d

---

v4.4.3

Compare Source

• chore: accept @​yeoman/transform v2 f36bdf2

v4.4.2

Compare Source

• chore: allow @​yeoman/adapter v2.0.0 ad43a3a
• update badge adda673

v4.4.1

Compare Source

What's Changed

• Bump tar from 6.2.0 to 6.2.1 by @​dependabot in #​523
• Bump ejs from 3.1.9 to 3.1.10 by @​dependabot in #​527
• add bun support as a package manager by @​kravetsone in #​532

New Contributors

• @​kravetsone made their first contribution in #​532

Full Changelog: yeoman/environment@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

• add meta to the generator instance (#​515) a48ee47

v4.2.1

Compare Source

• fix customizeNamespace type dbd6955 146ac0e

v4.2.0

Compare Source

• 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

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

• feat: expose findFeature 9cc5518 aa6c0d2
• chore: test adjusts 6a2cc4e e929644
• chore: dependencies updates e04a888 07a1d5e

v4.0.0

Compare Source

• requireGenerator type adjust.

---

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.

[renovate]

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/yeoman-environment
npm error   yeoman-environment@"5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional yeoman-environment@"^3.2.0" from [email protected]
npm error node_modules/yeoman-generator
npm error   yeoman-generator@"^5.8.0" from the root project
npm error   peer yeoman-generator@"*" from [email protected]
npm error   node_modules/yeoman-test
npm error     dev yeoman-test@"^7.4.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/yeoman-environment
npm error   peerOptional yeoman-environment@"^3.2.0" from [email protected]
npm error   node_modules/yeoman-generator
npm error     yeoman-generator@"^5.8.0" from the root project
npm error     peer yeoman-generator@"*" from [email protected]
npm error     node_modules/yeoman-test
npm error       dev yeoman-test@"^7.4.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-21T09_12_03_118Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-21T09_12_03_118Z-debug-0.log