Error: API rate limit exceeded for installation ID xx

[bharathkkb]

trafficstars

I was testing out a release config today and possibly due to some misconfig on my part I ended up with https://github.com/bharathkkb/mono-bp-test/runs/2661822325?check_suite_focus=true

Then subsequent runs showed as passed but actually didn't https://github.com/bharathkkb/mono-bp-test/runs/2661860431?check_suite_focus=true

Some searching seems to imply this is coming from GH possibly due to release-please querying something however this means I have to wait ( ~1 hr) to continue testing. It would be great if

• we could fail after a reasonable number of API calls or allow user configurability
• show status correctly in subsequent runs

[rabraghib]

the error was just cause you didnt specify bootstrap-sha in your release-please-config.json file.

[junaidbinfarooq]

We recently set up this action and were faced with this issue right from the start. While searching for this, I came to know that I may need to add bootstrap-sha considering the fact that we have an existing codebase and not a new one. So I added a .release-please-manifest.json with the following info:

{
  ".": "1.1.1",
  "bootstrap-sha": "last_release_commit_id"
}

But the error doesn't go away. Moreover, while adding the action to our workflow, we used the default template for the workflow shown in the action documentation and added the following options under with:

release-type: php
package-name: our_package_name

What could we be doing wrong? Besides, we are not sure what is this installation id?

[live627]

Same here. I want to use the manifestcommand for my PHP projects but when testing I noticed that the manifest command combined with the php release type hangs for several minutes until the API limit is spent. using node worked as expected because it is documented. is that document updated @bcoe?

What determinees the calls? One call for each commit made since the last tag?

@junaidbinfarooq I think the installatin ID is a unique repo number.

[bcoe]

@live627 unfortunately not sure what's going on with PHP release-type, it may be we don't have it working properly with the manifest releaser and will need to refactor a bit.

[dkarter]

I have encountered this issue as well with a simple release type. It worked the first time I added release-please to my ci file (PR created), but it had the wrong version so I closed the PR, updated my tags and tried again. Since then it is no longer working and giving the same API call limit error.

https://github.com/dkarter/dotfiles/runs/6549556709?check_suite_focus=true

Adding the manifest file did not help

[bcoe]

Relabeling as feature request, @bharathkkb indicated that what they'd like to see, is release-please detecting a serious misconfiguration, and aborting earlier.

@dkarter could you open an issue specific to the problems you're seeing, and the configuration you're using. As others have suggested, have you tried using a bootstrap-sha?

[dkarter]

Thanks @bcoe! I managed to resolve the issue on my end but can't remember how exactly. Everything is working now as expected.

[achamas-playco]

I had this problem when adding the action to an existing repo with a Node setup, whereas when I previously tested on a fresh repo with the workflow included from the start it worked fine. You need to get the bootstrapping setup right.

To fix it, I removed the .yml workflow file and essentially stripped the repo of any release-please content (any *release-please* configs if you'd been trying to get them working like I did).

I then created a release-please-config.json file in the repo root with:

{
  "bootstrap-sha": "<THE_BOOTSTRAP_SHA>",
  "release-type": "node",
  "packages": {
    ".": {}
  }
}

Note the bootstrap-sha must be a full SHA.

I also added the.release-please-manifest.json file in the root starting from the version I wanted 2.0.0 with:

{ ".": "2.0.0" }

I then copied the workflow example from the documentation and kept just the release part (good to know you could add deploy or publish after that with if: ${{ steps.release.outputs.releases_created }}).

on:
  push:
    branches:
      - main
name: Run Release Please
jobs:
  release-please:
    runs-on: ubuntu-latest
    steps:
      - uses: google-github-actions/release-please-action@v2
        id: release
        with:
          command: manifest
          token: ${{secrets.GITHUB_TOKEN}}
          default-branch: main

I then created a branch with those changes, and raised a PR to merge that back into the target branch main. The error stopped happening and my releases were created.

Hope that helps.

[ddennis]

I am also experiencing this issues - even after adding a

"bootstrap-sha": "8ec612df76d**************66604770"

Any pointers on what to look for ?

[asaff1]

I can say I'm facing the same problem with release type "python". Can someone explain, what types of API calls release please action do?