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

chore: update dependency @npmcli/map-workspaces to v4 #10734

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 13, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@npmcli/map-workspaces ^3.0.6 -> ^4.0.2 age adoption passing confidence

Release Notes

npm/map-workspaces (@​npmcli/map-workspaces)

v4.0.2

Compare Source

Bug Fixes
Chores

v4.0.1

Compare Source

Dependencies

v4.0.0

Compare Source

⚠️ BREAKING CHANGES
  • @npmcli/map-workspaces now supports node ^18.17.0 || >=20.5.0
Bug Fixes
Dependencies
Chores

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 renovate bot added the dependencies Pull requests that update a dependency file label Nov 13, 2024
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/npmcli-map-workspaces-4.x branch from 8f6cf02 to a314d9a Compare November 20, 2024 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants