You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a repo with many (1,955) releases, we observed the getting latest release step taking almost 4 minutes:
Wed, 29 May 2024 19:05:19 GMT [go-semantic-release]: getting latest release...
Wed, 29 May 2024 19:09:08 GMT [go-semantic-release]: found version: 3.0.2
I believe this happens because the calling code in semantic-release calls GetReleases with no matchRegex and ends up fetching every release that has ever been created.
I'm not sure why this is necessary, but if it could retrieve less releases then this step could be much faster. For example, retrieving the last 30 releases only takes about 2 seconds...
The text was updated successfully, but these errors were encountered:
Hi @jessebye, yes, you are right. This case should be handled better. I have to think a bit more about how we can solve this in a non-breaking manner because, currently, semantic-release needs all tags to find the latest release.
On a repo with many (1,955) releases, we observed the
getting latest release
step taking almost 4 minutes:I believe this happens because the calling code in semantic-release calls GetReleases with no matchRegex and ends up fetching every release that has ever been created.
I'm not sure why this is necessary, but if it could retrieve less releases then this step could be much faster. For example, retrieving the last 30 releases only takes about 2 seconds...
The text was updated successfully, but these errors were encountered: