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

pip requirements.txt: replacementVersion error without version specifier #33771

Open
rarkins opened this issue Jan 22, 2025 · 0 comments
Open
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:bug Bug fix of existing functionality

Comments

@rarkins
Copy link
Collaborator

rarkins commented Jan 22, 2025

Discussed in #33652

Originally posted by Wurstnase January 16, 2025

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

"renovateVersion": "39.113.0"

Please tell us more about your question or problem

I try to replace a package in a requirements.txt file. Without a version specifier, e.g. ==, it will fail because it will concat the replacementName with the replacementVersion without a version specifier.

Please check the following minimal to reproduce: https://github.com/Wurstnase/renovate_replacement

Logs (if relevant)

Logs

DEBUG: depName mismatch (repository=Wurstnase/renovate_replacement, packageFile=requirements.txt, branch=renovate/pip-replacement)
       "manager": "pip_requirements",
       "currentDepName": "pip",
       "newDepName": "uv0.5.20"
DEBUG: Found currentValue at index 3 (repository=Wurstnase/renovate_replacement, packageFile=requirements.txt, branch=renovate/pip-replacement)
       "currentValue": "==24.3.1"
 WARN: Error updating branch: update failure (repository=Wurstnase/renovate_replacement, branch=renovate/pip-replacement)

Reproduction forked to https://github.com/renovate-reproductions/33652

@rarkins rarkins added priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:bug Bug fix of existing functionality labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:bug Bug fix of existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant