bundler: git-refs support, with git tags in form of v1.2.3
wants to upgrade to vv1.2.3
#33005
Replies: 3 comments 4 replies
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
I was able to work around this issue on self-hosted by using the following {
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": ["config:recommended"],
"packageRules": [
{
"matchDatasources": ["git-refs"],
"matchManagers": ["bundler"],
"extractVersion": "^v?(?<version>.*)$"
}
]
} Not sure whether this is an expected config step though. If it is, should this be mentioned in the docs? |
Beta Was this translation helpful? Give feedback.
-
Converted to issue #33807 |
Beta Was this translation helpful? Give feedback.
-
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.
platform=local, version=39.60.0 (but also seen on platform=gitlab, version=>=39.47.0)
Please tell us more about your question or problem
Reproduction repo: https://github.com/siebertm/renovate-bundler-git-refs-issue-repro
We've been waiting for #32362 to arrive, as this was one of the features missing for our workflows. Thanks for implementing that!
Unfortunately, it's not working for us :-/
For a simple reproduction case, create a new folder with the following
Gemfile
Run
bundle install
, which generates a lockfile.create a
renovate.json
file to get startedWhen running renovate on this repo (
LOG_LEVEL=debug npx renovate --platform=local
), we'd expect renovate to upgraderails
tov7.2.2
tag. Instead, it findsv7.2.2
version but wants to change the tag tovv7.2.2
(with an additionalv
prefix).The relevant log entries for this (see
newValue
):I could not find in the code why this would happen, nor any existing report of this issue. Please guide me what to check for!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions