Standard usage of easy-release often results in multiple runs of the easy-release-changelog action for each PR submitted against a repository. Each run of the action takes about 10 seconds, but because of how GitHub does accounting for Actions each of these runs is counted as a minute of Actions usage. As of June 2026, public repositories on GitHub have unlimited Actions minutes, but private repositories do not. On private repositories with larger PR volume and a limited action budget, it's likely that people could consume large amounts of their Actions budget on easy-release-changelog runs.
Unfortunately there isn't a simple solution for this.
I think that the answer lies in re-implementing most of this logic as GitHub App instead of as a pair of actions, however this would require hosting the app. I haven't investigated this much, but if this becomes a problem then this is something we should probably consider. Based on some very limited research it seems that CloudFlare runners would likely be able to cover usage in their free tier until this sees widespread adoption.
No changes to make today, just documenting this as a known issue.
Standard usage of easy-release often results in multiple runs of the easy-release-changelog action for each PR submitted against a repository. Each run of the action takes about 10 seconds, but because of how GitHub does accounting for Actions each of these runs is counted as a minute of Actions usage. As of June 2026, public repositories on GitHub have unlimited Actions minutes, but private repositories do not. On private repositories with larger PR volume and a limited action budget, it's likely that people could consume large amounts of their Actions budget on easy-release-changelog runs.
Unfortunately there isn't a simple solution for this.
I think that the answer lies in re-implementing most of this logic as GitHub App instead of as a pair of actions, however this would require hosting the app. I haven't investigated this much, but if this becomes a problem then this is something we should probably consider. Based on some very limited research it seems that CloudFlare runners would likely be able to cover usage in their free tier until this sees widespread adoption.
No changes to make today, just documenting this as a known issue.