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

Update dependency pm2 to v6 #981

Merged
merged 1 commit into from
Mar 15, 2025
Merged

Update dependency pm2 to v6 #981

merged 1 commit into from
Mar 15, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 15, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pm2 (source) ^5.4.2 -> ^6.0.0 age adoption passing confidence

Release Notes

Unitech/pm2 (pm2)

v6.0.5

Compare Source


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

Copy link
Contributor

Review

Issues Found:

  1. Node Version Requirement Increase:
    • File: package-lock.json and package.json
    • Line: engines field in package.json and package-lock.json
    • Issue: The engines field in package.json and package-lock.json now requires Node.js version >=16.0.0. This is a significant change as it may not be compatible with existing environments that use older Node.js versions.
    • Suggestion: Ensure that the new Node.js version requirement is compatible with your deployment environments. If not, consider staying on the previous version of pm2 or updating your Node.js version.

Summary:

  • The update to pm2 v6 increases the required Node.js version to >=16.0.0. Ensure compatibility with your deployment environments before merging.

If you are confident that your environment supports Node.js 16 or higher, this update should be safe to merge.

@felladrin felladrin merged commit c236249 into main Mar 15, 2025
3 checks passed
@felladrin felladrin deleted the renovate/pm2-6.x branch March 15, 2025 19:44
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.

1 participant