Too long invocation on repos with large amount of releases

[lancedikson]

Hi! We started to experience troubles with running release-please on older packages that already have more than 1000 releases, and it takes more than 1.5 minutes to gather details about all the releases and then propose a new version. Is there a way to control that somehow (I couldn't find any in the Readme.md)? If not, could this be implemented? For example, limiting the number of releases read from GitHub could maybe work, but I don't fully understand the importance of fetching the whole list of releases, so I might be missing an important detail here 🤔
Our release-please action log mainly consists of these messages:

Running release-please version: 17.1.3
❯ Fetching package.json from branch master
✔ Looking for latest release on branch: master with prefix: videoly-core
❯ Fetching merge commits on branch master with cursor: undefined
❯ Found latest release pull request: 2950 version: 19.161.4
❯ Fetching releases with cursor undefined
❯ found release for videoly-core Version {
  major: 19,
  minor: 161,
  patch: 3,
  preRelease: undefined,
  build: undefined
}
❯ SHA not found in recent commits to branch master, skipping
❯ found release for videoly-core Version {
  major: 19,
  minor: 161,
  patch: 2,
  preRelease: undefined,
  build: undefined
}
❯ SHA not found in recent commits to branch master, skipping
❯ found release for videoly-core Version {
  major: 19,
  minor: 161,
  patch: 1,
  preRelease: undefined,
  build: undefined
}
❯ SHA not found in recent commits to branch master, skipping
❯ found release for videoly-core Version {
  major: 19,
  minor: 161,
  patch: 0,
  preRelease: undefined,
  build: undefined
}
...

[SoulPancake]

I think a very nice hack that I ended up using in some of the cases was the bootstrap-commit-sha
I know it should have a better solution but this might just save a lot of hours of your cumulative action runs
@lancedikson