@witty-crayon-22786 - seems that caching

~/.cache

wasn't the problem, it happened again on a clean build