fix(jsonata): updates when version and digest changed (#36461)

[jalil-salame]

Changes

• added a regression test for the issue discussed in `custom.jsonata`: manager can't update both the `currentDigest` and the `currentVersion` #36461 (taken from fix(jsonata): Updates with changes to digest and version (#36461) #37976)
• changed the logic in auto-replace to consider the number of changes to be made.
  If more than one change needs to be made and replaceString is not set then also set replaceWithoutReplaceString.

Context

Please select one of the below:

• This closes an existing Issue: #
• This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.

• No — I did not use AI for this contribution.
• Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
• Yes — substantive assistance (AI generated non‑trivial portions of code, tests, or documentation).
• Yes — other (please describe):

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

The public repository:

[github-actions]

Hi there,

You are using done comments which cause a lot of noise/notifications. Instead, please use GitHub's web interface to request another review. Please read our contributing guidelines to reduce noise.

Good luck,

The Renovate team

[renovate-release]

🎉 This PR is included in version 41.119.3 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 41.119.3

Your semantic-release bot 📦🚀

[RahulGautamSingh]

We are basing it on the fact that when only currentDigest is getting updated currentDigestShort will also be defined, which makes the change count > 1, right? @jalil-salame

[jalil-salame]

Did it cause a regression? I don't know if both currentDigest and currentDigestShort are defined

[jalil-salame]

In my tests only currentDigest was defined

[RahulGautamSingh]

Did it cause a regression?

No such cases as of now. I am just trying to understand the thinking behind the change

[jalil-salame]

Originally, if replaceString was undefined the code would set it to currentValue (version) or currentDigest (the first that was not undefined). Then it would try to replace the value in replaceString with the newValue and newDigest.

E.g regex manager:

# From this data
replaceString = "python:3.12@sha256:badbeef"
currentValue = "3.12"
currentDigest = "badbeef"
newValue = "3.13"
newDigest = "abcdef"
# It generates this string
replaceWith = "python:3.13@sha256:abcdef"

This doesn't work for the jsonata manager, since it doesn't provide a replaceString:

# From this data
replaceString = undefined (thus defaulted to currentValue)
currentValue = "3.12"
currentDigest = "badbeef"
newValue = "3.13"
newDigest = "abcdef"
# It generates this string
replaceWith = "3.13" # notice the digest is missing

It will then perform the update with replaceString === currentValue thus missing the currentDigest and failing to update.

The code changes the logic so it doesn't set the replaceString if there is more than one update:

# From this data
replaceString = undefined (thus defaulted to currentValue)
currentValue = "3.12"
currentDigest = "badbeef"
newValue = "3.13"
newDigest = "abcdef"
# Don't use replaceString since it was undefined and we have a newValue and newDigest

This reuses the codepath that was used to update the depName.

[RahulGautamSingh]

Sounds good