GitHub API Rate Limit

[mdgreenwald]

There are times where the workflow/action can hit the GitHub API Rate Limit and to reduce the occurrence of this the option to pass a token could be added.

Warning: Cannot get the latest Sops info from https://api.github.com/repos/mozilla/sops/releases. Error HTTPError: Unexpected HTTP response: 403

More information here:
actions/toolkit#986

Example here:
https://github.com/actions/setup-node/pull/595/files

[zsolt-p]

I'd add to this that if this occurs, and the latest version isn't able to be pulled, it falls back to a default version which may be different from the latest, which is not 100% what the user would expect. But since it's logged as a Warning, the workflow won't fail. Could this behaviour be customised? i.e. allow erroring/failing (not just warning) the workflow in case anything didn't go as intended?

[ChristianIvicevic]

It looks like this exact rate limit has been the cause for one of my workflows to get stuck with sops attempting to open an interactive terminal due to falling back to an older version. I can't say without a doubt that the rate limit is the exact cause, but it feels like it. After manually declaring the version instead of relying on latest I wasn't experiencing the issue of falling back to interactive terminals anymore.