What does a packageFiles with updates entry look like for a case like this? e.g. if it's got a package file value of 1.2 and latest version is 1.3.4 will currentVersion=1.3.4? I want to make sure this works end-to-end

Yes, and I can't actually reproduce it, because no versions left greater than the latest one, so everything gets filtered out, and getNewValue is never called (even when the locked version is lower).

Checkout reproduction repo: https://github.com/renovate-testing/test-19809-fix-replace-strategy

But yes, when I use debugger and trick the currentVersion to be lower one, it filters out upgrade based on this condition (see line 720):

• renovate/lib/workers/repository/process/lookup/index.ts

  Lines 710 to 725 in c6af925

  	res.updates = res.updates
  	.filter(
  	(update) => update.newValue !== null || config.currentValue === null,
  	)
  	.filter((update) => update.newDigest !== null)
  	.filter(
  	(update) =>
  	(is.string(update.newName) &&
  	update.newName !== config.packageName) ||
  	update.isReplacement === true ||
  	update.newValue !== config.currentValue ||
  	update.isLockfileUpdate === true ||
  	// TODO #22198
  	(update.newDigest &&
  	!update.newDigest.startsWith(config.currentDigest!)),
  	);

So maybe this bug isn't really a bug anymore because it can't happen?

🎉 This PR is included in version 39.125.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀