Update dependency yeoman-environment to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
yeoman-environment (source)	^3.15.1 → ^6.0.0

---

Release Notes

yeoman/environment (yeoman-environment)

v6.0.1

Compare Source

What's Changed

• fix: ask before installing local packages by @​mshima in #​753
• chore(release): bump version to v6.0.1 by @​github-actions[bot] in #​757

Full Changelog: yeoman/environment@v6.0.0...v6.0.1

v6.0.0

Compare Source

🚀 yeoman-environment v6 – Release Notes

• Switch to @​yeoman/adapter v4 (and inquirer v13) by default.
  Some behavior changes may happen.

---

v5.1.3

Compare Source

• fix: only fallback to import if requiring fails with esm/async error (#​716) e4fb745

---

v5.1.2

Compare Source

• fix: use globbySync to resolve PNPM global node_modules paths (#​692) 4317fef

---

v5.1.1

Compare Source

• feat: lookup for generators in pnpm global folder (#​680) 2fcd028

---

v5.1.0

Compare Source

• chore(deps): bump globby from 15.0.0 to 16.0.0 (#​676) cd962ec
• chore(deps): bump @​yeoman/conflicter from 3.0.0 to 4.0.0 (#​677) 04a104b
• chore(deps): bump globby from 14.1.0 to 15.0.0 (#​662) 5d39217
• feat: add generatorLookupOptions option (#​674) a301ab8
• fix: expose missing types (#​673) 4de747f

---

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: (UTC)

• Branch creation
  • Monday through Friday (* * * * 1-5)
• 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.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Test
• Failed Step: Run yarn
• Run: View failed run
  What failed: Incompatible Node.js version for yeoman-environment@6.0.0
  Why: The error message indicates that the yeoman-environment@6.0.0 module is incompatible with the current Node.js version (16.20.2). This is a code issue, as the project dependencies are not compatible with the runtime environment.
  Action:
  Update the project dependencies to use a compatible Node.js version, or update the Node.js version used in the CI workflow.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Test
• Failed Step: Run yarn
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.