feat: repositoryCache

[rarkins]

Adds a new capability to cache manager extract results per-branch. If the commit as well as the config haven't changed then the previously extracted results are reused.

[viceice]

Shouldn't we try to have all caches with nearly same API and behavior? 🤔

[viceice]

Why using json files instead of global cache?

I think a checkbox in master issue for repo cache clean on next run makes sense.

[rarkins]

Why using json files instead of global cache?

From a "layered security" point of view, the global cache should contain as little provate information as possible, in case there were ever a leak. I renamed it to "package cache" recently to reflect that, and will keep trying to tighten it up. Whereas this repo cache should have a better level of protection in the app (I will ensure it's copied and erased after each repo).

For typical users, these JSON files are essentially going to sit alongside the global/package cache in ${config.cacheDir}/renovate/.

I think a checkbox in master issue for repo cache clean on next run makes sense.

Yes, that would be a good feature to add, but I won't do it right away. For now the feature will default to false anyway.

[rarkins]

@viceice ready to merge this now with limited API but using types instead. please let me know if you spot any problems

[viceice]

I'm ok with it for now, as it's experimental and disabled by default. We can optimize the api later.

Just some small suggestions.

[renovate-release]

🎉 This PR is included in version 21.21.0 🎉

The release is available on:

• GitHub release
• 21.21.0

Your semantic-release bot 📦🚀