Reason for the maxTagsToFetch Limit

[oliver-car]

https://github.com/ietf-tools/semver-action/blob/2415a9e79db34eb828a8dc1d20d4890725737227/dist/index.js#L52964

Hi, just wanted to understand what the reason for the 100 commit limit is.
It's causing some pipelines to fail due to the latest change being further back than 100 commits.
Is there a nice way around this?
Alternatively, could the limit be dropped or a limit override be made available?

[NGPixel]

This is a tags limit, not commits. All commits will be fetched, whether it's 10 or 1000.

100 is the maximum tags that can be fetched in a single graphQL query to GitHub. I'm not sure I understand the use case where you need to go back further than 100 tags?

[oliver-car]

we use a mono-repo with many services, often times it's not finding tags for specific services due to more active services totalling over 100 tags pushed since the most recent tag of the less updated service
we forked the repository and made the update so it appears to be possible to go further back than 100