Action failed - Fetching merge commits on branch main with cursor: undefined

[mikebell]

TL;DR

I have an existing release-please PR open (https://github.com/ministryofjustice/cloud-platform-mtm/pull/4) I was developing more functionality on another branch and merged it in to main (release-please PR still open). The action failed with

Error: release-please failed: Request failed due to following response errors:
 - Something went wrong while executing your query. Please include `8C64:2A9B24:30E4B27A:312CD2AE:663A3FEC` when reporting this issue.

Expected behavior

Existing release-please PR should parse the updated commit history and update the open PR with new changes

Observed behavior

When I merged in my feature PR the pipeline failed

Action YAML

name: Build package

on:
  push:
    branches: [main]

permissions:
  contents: write
  pull-requests: write

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: GoogleCloudPlatform/release-please-action@v4
        id: release
        with:
          release-type: python
      - uses: actions/checkout@v4
      - name: Install Python
        uses: actions/setup-python@v5
        with:
          python-version: '3.12'
      - name: Install poetry
        uses: abatilo/actions-poetry@v2
      - uses: actions/cache@v4
        name: Define a cache for the virtual environment based on the dependencies lock file
        with:
          path: ./.venv
          key: venv-${{ hashFiles('poetry.lock') }}
      - name: Install the project dependencies
        run: poetry install
      - name: Build package
        run: poetry build
      - name: Upload Release Artifact
        if: ${{ steps.release.outputs.release_created }}
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: gh release upload ${{ steps.release.outputs.tag_name }} ./dist/*

Log output

2024-05-07T14:51:20.7829863Z Current runner version: '2.316.1'
2024-05-07T14:51:20.7853595Z ##[group]Operating System
2024-05-07T14:51:20.7854265Z Ubuntu
2024-05-07T14:51:20.7854601Z 22.04.4
2024-05-07T14:51:20.7855003Z LTS
2024-05-07T14:51:20.7855335Z ##[endgroup]
2024-05-07T14:51:20.7855710Z ##[group]Runner Image
2024-05-07T14:51:20.7856217Z Image: ubuntu-22.04
2024-05-07T14:51:20.7856616Z Version: 20240422.1.0
2024-05-07T14:51:20.7857606Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240422.1/images/ubuntu/Ubuntu2204-Readme.md
2024-05-07T14:51:20.7859055Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240422.1
2024-05-07T14:51:20.7859902Z ##[endgroup]
2024-05-07T14:51:20.7860310Z ##[group]Runner Image Provisioner
2024-05-07T14:51:20.7860824Z 2.0.369.1
2024-05-07T14:51:20.7861165Z ##[endgroup]
2024-05-07T14:51:20.7862173Z ##[group]GITHUB_TOKEN Permissions
2024-05-07T14:51:20.7863822Z Contents: write
2024-05-07T14:51:20.7864261Z Metadata: read
2024-05-07T14:51:20.7864933Z PullRequests: write
2024-05-07T14:51:20.7865428Z ##[endgroup]
2024-05-07T14:51:20.7868596Z Secret source: Actions
2024-05-07T14:51:20.7869178Z Prepare workflow directory
2024-05-07T14:51:20.8491080Z Prepare all required actions
2024-05-07T14:51:20.8649639Z Getting action download info
2024-05-07T14:51:21.1337903Z Download action repository 'GoogleCloudPlatform/release-please-action@v4' (SHA:a37ac6e4f6449ce8b3f7607e4d97d0146028dc0b)
2024-05-07T14:51:21.7593001Z Download action repository 'actions/checkout@v4' (SHA:0ad4b8fadaa221de15dcec353f45205ec38ea70b)
2024-05-07T14:51:22.2577745Z Download action repository 'actions/setup-python@v5' (SHA:82c7e631bb3cdc910f68e0081d67478d79c6982d)
2024-05-07T14:51:22.8062917Z Download action repository 'abatilo/actions-poetry@v2' (SHA:c31426b23a8080795905ec73c9e458a2447cb2f2)
2024-05-07T14:51:23.1683822Z Download action repository 'actions/cache@v4' (SHA:0c45773b623bea8c8e75f6c82b208c3cf94ea4f9)
2024-05-07T14:51:23.3856292Z Complete job name: build
2024-05-07T14:51:23.4756855Z ##[group]Run GoogleCloudPlatform/release-please-action@v4
2024-05-07T14:51:23.4757535Z with:
2024-05-07T14:51:23.4757874Z   release-type: python
2024-05-07T14:51:23.4758403Z   token: ***
2024-05-07T14:51:23.4758902Z   repo-url: ministryofjustice/cloud-platform-mtm
2024-05-07T14:51:23.4759383Z   github-api-url: https://api.github.com
2024-05-07T14:51:23.4759925Z   github-graphql-url: https://api.github.com/graphql
2024-05-07T14:51:23.4760472Z   fork: false
2024-05-07T14:51:23.4760788Z   include-component-in-tag: false
2024-05-07T14:51:23.4761235Z   skip-github-release: false
2024-05-07T14:51:23.4761699Z   skip-github-pull-request: false
2024-05-07T14:51:23.4762086Z   changelog-host: https://github.com
2024-05-07T14:51:23.4762514Z ##[endgroup]
2024-05-07T14:51:23.8681298Z Running release-please version: 16.10.0
2024-05-07T14:51:24.2111229Z ✔ Looking for latest release on branch: main with prefix: 
2024-05-07T14:51:24.2112515Z ❯ Fetching merge commits on branch main with cursor: undefined
2024-05-07T14:51:28.7445165Z ##[error]release-please failed: Request failed due to following response errors:
 - Something went wrong while executing your query. Please include `8C64:2A9B24:30E4B27A:312CD2AE:663A3FEC` when reporting this issue.
2024-05-07T14:51:28.7837251Z Cleaning up orphan processes

Additional information

No response

[JanMaleta]

Can confirm, I encountered the same error, which started around an hour ago.

[jbottigliero]

Also started encountering this on both v3 and v4 branches. There does appear to be some likely related GitHub incidents at https://www.githubstatus.com/ for those landing here.

[AnzhiZhang]

I have the same error, github is still down right now

[kenodressel]

I have the exact same issue. Runs: working: https://github.com/aeternity/tipping-community-backend/actions/runs/8983221229/job/24672501841 changing something unrelated (and broken): https://github.com/aeternity/tipping-community-backend/actions/runs/8987487831/job/24687766859

[kenodressel]

Resolved for me.

[goekhancimsir]

Resolved for me.

Same goes for me.

[ehakan]

We had the issue around the same time, I thought the problem was us pushing two commits to main at the same time, but seems like an unrelated small incident blip. Currently fixed for us as well.

[mikebell]

Seems to be working now.