From 6fb00550cc3e6f39d61f38b74e5f065c0a322d4a Mon Sep 17 00:00:00 2001
From: Christoph Wurst <1374172+ChristophWurst@users.noreply.github.com>
Date: Wed, 29 Apr 2026 21:04:08 +0200
Subject: [PATCH] chore(renovate): use currentValue instead of currentVersion
 in commit message

Using currentVersion resolves to the locked version from the lockfile,
which can make bump PRs appear as downgrades when the range is being bumped
forward. currentValue correctly reflects the range constraint in package.json.

AI-assisted: OpenCode (claude-sonnet-4.6)
Signed-off-by: Christoph Wurst <1374172+ChristophWurst@users.noreply.github.com>
---
 renovate.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/renovate.json b/renovate.json
index 3bc89dfea7..12dcabff44 100644
--- a/renovate.json
+++ b/renovate.json
@@ -17,7 +17,7 @@
 	],
 	"commitMessageAction": "Bump",
 	"commitMessageTopic": "{{depName}}",
-	"commitMessageExtra": "from {{currentVersion}} to {{#if isPinDigest}}{{{newDigestShort}}}{{else}}{{#if isMajor}}{{prettyNewMajor}}{{else}}{{#if isSingleVersion}}{{prettyNewVersion}}{{else}}{{#if newValue}}{{{newValue}}}{{else}}{{{newDigestShort}}}{{/if}}{{/if}}{{/if}}{{/if}}",
+	"commitMessageExtra": "from {{currentValue}} to {{#if isPinDigest}}{{{newDigestShort}}}{{else}}{{#if isMajor}}{{prettyNewMajor}}{{else}}{{#if isSingleVersion}}{{prettyNewVersion}}{{else}}{{#if newValue}}{{{newValue}}}{{else}}{{{newDigestShort}}}{{/if}}{{/if}}{{/if}}{{/if}}",
 	"rangeStrategy": "bump",
 	"minimumReleaseAge": "7 days",
 	"rebaseWhen": "conflicted",