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(versioning/pep440): log debug message if newVersion is excluded from range #28950

Merged

Conversation

RahulGautamSingh
Copy link
Collaborator

Changes

Add an if-statement to check if the newVersion is excluded from range, so that we can return early and also log a more informational debug message instead of the less useful warning we displaly currently.

Context

Closes: #25501

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

rarkins
rarkins previously approved these changes May 9, 2024
@rarkins rarkins merged commit ad9d2b9 into renovatebot:main May 9, 2024
34 checks passed
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 37.351.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@@ -191,6 +203,7 @@ export function getNewValue({
newVersion,
);

// istanbul ignore if
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should add a test instead

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.

pep440: failed to calculate newValue
4 participants