getting error: release-please failed: fetch failed

[victor-wang-anz]

Thanks for stopping by to ask us a question! Please make sure to include:

• I just upgraded the release please to v4 and updated my config, but now getting error: release-please failed: fetch failed

below is my yaml:

      - name: Run Release Please
        uses: ./.actions/release-please-action
        with:
          token: xxx
          config-file: release-please-config.json
          manifest-file: .release-please-manifest.json
          target-branch: main
          proxy-server: localhost:3128

error:

Run ./.actions/release-please-action
  with:
    token: ***
    config-file: release-please-config.json
    manifest-file: .release-please-manifest.json
    target-branch: main
    proxy-server: localhost:3128
    repo-url: xxx
    github-api-url: https://api.github.com
    github-graphql-url: https://api.github.com/graphql
    fork: false
    include-component-in-tag: false
    skip-github-release: false
    skip-github-pull-request: false
    changelog-host: https://github.com
Running release-please version: 16.12.0
❯ Fetching release-please-config.json from branch main
❯ Fetching .release-please-manifest.json from branch main
Error: release-please failed: fetch failed

2nd error after some change

Run ./.actions/release-please-action
  
Running release-please version: 16.12.0
✔ Looking for latest release on branch: main with prefix: 
❯ Fetching merge commits on branch main with cursor: undefined
Error: release-please failed: fetch failed

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

[chris-mac]

Any update on this issue? Seeing the same behaviour when running on self-hosted runners behind proxy.
Have tried multiple versions including much older ones but still see fetch failed. Suspect an upgraded dependency somewhere in the chain?

[kbalston]

Seeing the same behaviour when running on self-hosted runners behind proxy.

We're also seeing the same Error: release-please failed: fetch failed failure for our self-hosted runners behind a corporate proxy

[Aigle200]

yes