Find the cause why config.isLockFileMaintenance is not working as expected

[rarkins]

we need to find the cause why is not working as expected.

Your pr is a workaround and not a fix for the root cause.

Originally posted by @viceice in #9695 (comment)

[trim21]

dashboard isn't updated either in the provided repo, didn't know if these bugs are relative.

[viceice]

dashboard isn't updated either in the provided repo, didn't know if these bugs are relative.

This happen when renovate automerge a branch /pr. Dashboard will be updated on next run. There is an existing issue somewhere around.

[msw-kialo]

After a longer debugging session I suspect this is broken for all managers that use it (I had the issues with pip-compile): Based of the code in lib/workers/repository/updates/flatten.ts I think that this updateType is simply set

renovate/lib/workers/repository/updates/flatten.ts

Line 130 in ec723e3

lockFileConfig.updateType = 'lockFileMaintenance';

after the is* properties are:

renovate/lib/workers/repository/updates/flatten.ts

Lines 90 to 97 in ec723e3

	if (updateConfig.updateType) {
	updateConfig[`is${upper(updateConfig.updateType)}`] = true;
	}
	if (updateConfig.updateTypes) {
	updateConfig.updateTypes.forEach((updateType) => {
	updateConfig[`is${upper(updateType)}`] = true;
	});
	}

Adding lockFileConfig.isLockfileUpdate = true; locally afterwards fixed the issue for me, but I am not sure whether this is the proper fix.

[renovate-release]

🎉 This issue has been resolved in version 31.66.5 🎉

The release is available on:

• GitHub release
• 31.66.5

Your semantic-release bot 📦🚀