Update the release version in CHANGELOG.md and VERSION #7599
Conversation
renovate.json
Outdated
| @@ -3,15 +3,15 @@ | |||
| "extends": [ | |||
| "config:base" | |||
| ], | |||
| "baseBranches": ["main", "release-2.11", "release-2.10"], | |||
| "baseBranches": ["main", "release-2.12", "release-2.11"], | |||
There was a problem hiding this comment.
Does renovate look at this file on the branch?
There was a problem hiding this comment.
I am not sure. But it is better to keep this one up-to-date too, at least for completeness.
There was a problem hiding this comment.
I disagree. I find it confusing to make unnecessary changes. If we want to include new branch, we should do it in file that's actually used.
Furthermore if we merge this branch into main after creating rc-0, we will effectively stop getting updates for release-2.10, even though release-2.12 wasn't released yet.
There was a problem hiding this comment.
Renovate always uses the config from the repository's default branch
There was a problem hiding this comment.
I have removed the changes I previously did in renovate.json, and I will now merge this PR.
Signed-off-by: Yuri Nikolic <durica.nikolic@grafana.com>
duricanikolic
force-pushed
the
yuri/release-2.12
branch
from
57e8595
to
7f9823b
Compare
duricanikolic
changed the title
What this PR does
This PR makes the following changes:
CHANGELOG.mdto2.12.0-rc.0.VERSIONto2.12.0-rc.0.Which issue(s) this PR fixes or relates to
Part of #7542
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX].about-versioning.mdupdated with experimental features.