Reproduction for renovatebot/renovate PR #43535

Demonstrates that the JSONata custom manager now honors autoReplaceStringTemplate.

Background

Microsoft Dynamics 365 Business Central requires 4-segment versions (major.minor.build.revision) in app.json. NuGet normalizes trailing-zero revisions away on the feed (27.0.0.0 is published as 27.0.0), so Renovate's newValue arrives as a 3-segment string. The BC compiler rejects a 3-segment write-back, so the user needs autoReplaceStringTemplate to pad the value back to 4 segments before it lands in the file.

This is the same class of problem covered in discussion #34567, but distinct from the digest issue fixed in June 2025. See PR #43535 for the fix.

Reproduction

• app.json — a minimal BC-style manifest with a dependency at 12.0.0.0 (NuGet has it as 12.0.0 on the feed).
• renovate.json — JSONata custom manager + autoReplaceStringTemplate that pads any 3-segment newValue back to 4 segments.

Expected behavior

Without the fix (current main): autoReplaceStringTemplate is silently ignored by the JSONata manager. Either:

• Renovate writes the 3-segment NuGet value (e.g. 13.0.3) into app.json, breaking the BC compiler, or
• the strict newValue comparison in confirmIfDepUpdated rejects the write-back and Renovate logs WORKER_FILE_UPDATE_FAILED.

With the fix (PR #43535): Renovate opens a PR updating 12.0.0.0 → 13.0.3.0 (template-padded to 4 segments).

Showcasing the fix requires running a Renovate build that includes PR #43535.