Renovate Unable to add multiple labels to gitlab MRs #30185
Replies: 2 comments 3 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:
Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
|
It turned out that for some reason Renovate is not handling the scoped labels e.g. renovate::python "labels": [
"renovate",
"{{{datasource}}}",
"{{{updateType}}}"
],The above is only on the top level of the renovate json file. |
Beta Was this translation helpful? Give feedback.
-
|
Can you reproduce the problem on github.com or is it specific to GitLab.com? |
Beta Was this translation helpful? Give feedback.
-
|
Hey @rarkins, It seems on github this is working properly:
On our selfhosted gitlab with the same renovate.json file it is failing to create all the labels though and the PRs are created as follows:
We are always getting the first scoped label ( If the PRs are not scoped it works e.g I also checked and I could manually add up to three labels for each PR. The full renovate.json file is: {
"labels": [
"renovate",
"renovate::{{{datasource}}}",
"renovate::{{{updateType}}}"
],
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended",
":enablePreCommit",
":semanticCommits",
":automergeMinor",
":automergeDigest",
":automergeLinters",
"mergeConfidence:all-badges"
],
"gitLabIgnoreApprovals": true,
"platformAutomerge": true,
"configMigration": true,
"customManagers": [
{
"description": "Manager to work through the custom defined version strings.",
"customType": "regex",
"fileMatch": [
"(^|/|\\.)([Dd]ocker|[Cc]ontainer)file$",
"(^|/)([Dd]ocker|[Cc]ontainer)file[^/]*$"
],
"matchStrings": [
"#\\s*renovate:\\s*datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?( registryUrl=(?<registryUrl>.*?))?\\sENV .*?_VERSION=\"(?<currentValue>.*)\"\\s",
"#\\s*renovate:\\s*datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?( registryUrl=(?<registryUrl>.*?))?\\s .*?_version: \"(?<currentValue>.*)\"\\s"
],
"versioningTemplate": "{{#if versioning}}{{{versioning}}}{{else}}semver-coerced{{/if}}"
}
],
"packageRules": [
{
"matchDatasources": [
"pypi"
],
"matchUpdateTypes": [
"minor",
"patch"
],
"groupName": "Pypi dependencies Minor and Patch"
},
{
"matchDatasources": [
"npm"
],
"matchUpdateTypes": [
"minor",
"patch"
],
"groupName": "NPM dependencies Minor and Patch"
},
{
"matchDatasources": [
"repology"
],
"matchUpdateTypes": [
"minor",
"patch"
],
"groupName": "Repology dependencies Minor and Patch"
}
]
}The Dockerfile that is being checked for updates: # renovate: datasource=repology depName=alpine_3_20/python3-dev versioning=loose
ENV PYTHON3_DEV_VERSION="3.11.3-r1"
# renovate: datasource=repology depName=alpine_3_20/py3-pip versioning=loose
ENV PY3_PIP_VERSION="23.0-r2"
# renovate: datasource=pypi depName=requests
ENV PYTHON_REQUESTS_VERSION="2.22.0"
# renovate: datasource=npm depName=express
ENV NPM_EXPRESS_VERSION="3.0.0"
# Install required packages
RUN apk add --no-cache \
curl="${CURL_VERSION}" \
python3-dev="${PYTHON3_DEV_VERSION}" \
py3-pip="$PY3_PIP_VERSION"
# Install python packages
RUN pip3 install --no-cache-dir \
requests=="${PYTHON_REQUESTS}" |
Beta Was this translation helpful? Give feedback.
-
|
Please create a minimal reproduction on github.com (working) and gitlab.com (non-working). |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab
Please tell us more about your question or problem
Hi,
When Running renovate I would like to have labels on my Merge Requests based on what kind of package is to be updated.
Unfortunately only the first label from the list is always added and the rest are discarded.
My Rules Configuration is as follows:
I tried combining the
labelsandaddLabelskeys for the major updates but then I was only getting the values from thelabelskey and theaddLabelskey was dropped.The only times I was getting more than one key was when I had
labelskey added on the top level configuration (value wasrenovate) and then all the MRs were gettingrenovatelabel + the first value of anaddLabellist from the packageRules e.g.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions