fix(versioning): strip v prefix when bumping semver ranges

[rarkins]

Changes

Ensure v prefixes are stripped from npm semver ranges when bumping ranges

Context

Fixes #24346

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

[viceice]

do we also trim v when current value has no v but new value?

[rarkins]

do we also trim v when current value has no v but new value?

What do you mean by this?

I was wondering if there's any scenario where the v is meant to be there and is in the currentValue, but that doesn't seem to be the same as what you're asking

[viceice]

do we also trim v when current value has no v but new value?

What do you mean by this?

I was wondering if there's any scenario where the v is meant to be there and is in the currentValue, but that doesn't seem to be the same as what you're asking

never mind, would probably cause more edge cases and issues

[renovate-release]

🎉 This PR is included in version 36.93.1 🎉

The release is available on:

• GitHub release
• 36.93.1

Your semantic-release bot 📦🚀