How can I invalidate the config cache?

[ReenigneArcher]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

No response

Please tell us more about your question or problem

Trying to debug a custom manager, and renovate keeps using a cached version of the org level config. It is even using a cached version after I told it to use a different branch.

Having the config file cached, makes it very difficult to test things out. How can I invalidate it?

Logs (if relevant)

Logs

DEBUG: Found renovate.json config file
DEBUG: Repository config
{
  "fileName": "renovate.json",
  "config": {
    "$schema": "https://docs.renovatebot.com/renovate-schema.json",
    "extends": [
      "local>LizardByte/.github:renovate-config#ReenigneArcher-patch-1"
    ]
  }
}

DEBUG: migrateAndValidate()
DEBUG: No config migration necessary
DEBUG: http cache: Using cached response: https://api.github.com/repos/LizardByte/.github/contents/renovate-config.json?ref=ReenigneArcher-patch-1 from 2026-04-10T13:23:20.654Z
DEBUG: http cache: Using cached response: https://api.github.com/repos/LizardByte/.github/contents/renovate-config.json5 from 2026-04-10T13:23:20.781Z

[ReenigneArcher]

AI has found this

I found the decisive behavior in Renovate’s code: in your exact log path, it never re-runs dependency extraction at all because the repository is still in onboarding and the cached onboarding PR is considered valid.

...

There’s a second important detail in the code: the onboarding PR “config hash” only hashes the renovate.json file stored in the onboarding branch, not the resolved contents of the inherited shared preset. So changing LizardByte/.github does not invalidate the existing onboarding PR automatically.

So basically I cannot have the onboarding PR ever updating just by updating my org level renovate config files. This makes it nearly impossible to get my renovate config to a state I am happy with before enabling it in all my repos. And even after several days it still doesn't update to the new org level config.

Can a button be added to the mend renovate UI that allows us to manually invalidate the cache?

[RahulGautamSingh]

UPDATE: I mistook repoCache for httpCache. Please ignore what I said below:

Need to set repositoryCache:"reset" or "disabled" if such option is available in the developer.mend.io UI.

Or update the repo with a new commit, we usually refresh cache if that's done.

Or, add an label in your config that affects none of the packages, so the config is different and cache is invalidated,

[ReenigneArcher]

Need to set repositoryCache:"reset" or "disabled" if such option is available in the developer.mend.io UI.

There's no where to set options like that in developer.mend.io UI.

Or update the repo with a new commit, we usually refresh cache if that's done.

I had this work on one repo, but not another.

Or, add an label in your config that affects none of the packages, so the config is different and cache is invalidated,

This makes it a real pain to go through onboarding. I have 40 repos, and don't want to be manually editing the onboarding PR config in so many repos until I get it tweaked properly. Ideally I could just edit the org level config and have renovate run again without a cached config.

[jamietanna]

To confirm, with:

DEBUG: http cache: Using cached response: https://api.github.com/repos/LizardByte/.github/contents/renovate-config.json?ref=ReenigneArcher-patch-1 from 2026-04-10T13:23:20.654Z

Can you confirm that there's been a push to that branch since then?

[ReenigneArcher]

There was a commit yesterday, I rebased the onboarding PR just now and it picked up the changes finally. I did this before and it didn't pick up the changes though.

Still, there should be a way to invalidate the cache manually.