Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getting error: release-please failed: fetch failed #1021

Open
victor-wang-anz opened this issue Jul 12, 2024 · 5 comments
Open

getting error: release-please failed: fetch failed #1021

victor-wang-anz opened this issue Jul 12, 2024 · 5 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@victor-wang-anz
Copy link

victor-wang-anz commented Jul 12, 2024

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.

@victor-wang-anz victor-wang-anz added priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue. labels Jul 12, 2024
@chris-mac
Copy link

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
Copy link

kbalston commented Jul 30, 2024

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
Copy link

yes

@araisch
Copy link

araisch commented Dec 2, 2024

Had this problem with runner behind corporate proxy as well. Issue got worse and worse. After trying several old releases I've found out it was probably a time-out problem. Firewall and Proxy delaying already and runner had a hanging process slowing down. So on good days he made it in time, but commonly he failed fetching..
Would propose an enhancement in debug logging, as error code 1 fetch failed is not really helpful..

@Stratus3D
Copy link

I'm currently encountering a similar issue for a public repo on GitHub - https://github.com/asdf-vm/asdf/actions/runs/13033494015/job/36358075137. On the weekends and early morning hours it succeeds, but during the workday it fails. Not clear if it's an issue with this action or the GitHub API itself. This is a currently blocking a release of mine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

6 participants