Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency yeoman-environment to v4 #34

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 23, 2023

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

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 - 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
Copy link
Contributor Author

renovate bot commented Oct 23, 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 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! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional yeoman-environment@"^3.2.0" from [email protected]
npm ERR! node_modules/yeoman-generator
npm ERR!   yeoman-generator@"^5.8.0" from the root project
npm ERR!   peer yeoman-generator@"*" from [email protected]
npm ERR!   node_modules/yeoman-test
npm ERR!     dev yeoman-test@"^7.4.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/yeoman-environment
npm ERR!   peerOptional yeoman-environment@"^3.2.0" from [email protected]
npm ERR!   node_modules/yeoman-generator
npm ERR!     yeoman-generator@"^5.8.0" from the root project
npm ERR!     peer yeoman-generator@"*" from [email protected]
npm ERR!     node_modules/yeoman-test
npm ERR!       dev yeoman-test@"^7.4.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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-09T22_06_07_939Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch 2 times, most recently from f2b1fd5 to 02136d2 Compare November 15, 2023 05:01
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch from 02136d2 to 26dec3c Compare January 15, 2024 19:00
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch from 26dec3c to b54073a Compare January 29, 2024 20:17
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch from b54073a to 99506da Compare March 9, 2024 22:06
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch from 99506da to dfbf54d Compare June 3, 2024 20:15
Copy link
Contributor Author

renovate bot commented Jun 3, 2024

⚠️ 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 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@"4.4.3" from the root project
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 Could not resolve dependency:
npm error peer yeoman-environment@"^3.13.0" 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   peer yeoman-environment@"^3.13.0" 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 /tmp/renovate/cache/others/npm/_logs/2024-12-09T04_00_27_187Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-09T04_00_27_187Z-debug-0.log

@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch 2 times, most recently from 31e2974 to 826a292 Compare October 14, 2024 20:56
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch 8 times, most recently from c0d80fd to c216c09 Compare November 13, 2024 08:00
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch from c216c09 to 5eae4df Compare November 13, 2024 08:10
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch from 5eae4df to e36ea43 Compare November 13, 2024 08:29
@renovate renovate bot changed the title fix(deps): update dependency yeoman-environment to v4 fix(deps): update dependency yeoman-environment to v4 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/yeoman-environment-4.x branch December 8, 2024 18:44
@renovate renovate bot changed the title fix(deps): update dependency yeoman-environment to v4 - autoclosed fix(deps): update dependency yeoman-environment to v4 Dec 9, 2024
@renovate renovate bot reopened this Dec 9, 2024
@renovate renovate bot force-pushed the renovate/yeoman-environment-4.x branch from 3c208a2 to e36ea43 Compare December 9, 2024 04:00
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