Skip to content

feat(manager/npm): use volta pins as constraints #35869

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

Merged
merged 5 commits into from
May 24, 2025

Conversation

RahulGautamSingh
Copy link
Collaborator

Changes

  • Use the extracted volta pins as constraints, prioritizing them over packageManager and engines values

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@RahulGautamSingh RahulGautamSingh marked this pull request as draft May 12, 2025 00:43
@RahulGautamSingh RahulGautamSingh marked this pull request as ready for review May 12, 2025 01:08
@rarkins rarkins requested review from viceice and rarkins May 12, 2025 10:35
@rarkins rarkins enabled auto-merge May 17, 2025 15:04
@RahulGautamSingh RahulGautamSingh requested a review from viceice May 18, 2025 04:16
@rarkins rarkins added this pull request to the merge queue May 24, 2025
Merged via the queue into renovatebot:main with commit e122523 May 24, 2025
40 checks passed
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 40.28.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

Renovate should detect node and npm constraints from Volta pins
5 participants