feat: Limit HTTP concurrency and frequency by default

[zharinov]

Changes

• Set default concurrency to 5 requests to a single host
• Allow 5 requests per second to a single host by default

Context

• Ref: refactor: Flatten update lookup tasks #27369

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Could these instead be in a default hostRules value?

[zharinov]

I think it doesn't make too much sense, since we still have to hard-code this default value if there is no host rules found.

[rarkins]

HostRules are mergeable so it should always be found? Plus has more visibility in config docs

[zharinov]

Unfortunately, it doesn't seem to work during testing nor during runtime.

[zharinov]

HostRuleSearchResult all-optional fields make me think it probably is not so easily fixable

[renovate-release]

🎉 This PR is included in version 37.228.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[erezrokah]

Hi 👋 I believe this caused our self hosted GitHub Action running time to increase from 10m to 2h, is there a way to disable it for all hosts? See #27759

[zharinov]

Hi @erezrokah, could you try this host rule:

"hostRules": [
  {
    "concurrentRequestLimit": 0,
    "maxRequestsPerSecond": 0
  }
]

It seems to work for my local setup, hopefully it will help you.

[zharinov]

@rarkins Should we somehow make unlimited default for actions?

And one more unrelated question: it's recommended to persist repository cache, but what about package cache? If it doesn't, would you recommend it?

[rarkins]

Which host/type is needing the increased rate and/or concurrency? I'm confused where/how actions comes into it

[rarkins]

Actually let's switch the discussion to #27759. We can revert this if necessary