codecov / codecov/codecov-action

[BUG] Bundle Analysis fails on GitHub Actions CI only - locally uploads fine.

Open
#1,946 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
1.7k
Forks
260
Avg merge
1d 7h
Merged PRs (30d)
1

Description

Describe the bug
Codecov bundle analyzer upload started failing in GitHub Actions with:
Failed to get pre-signed URL, bad response: "404 - Not Found".
This previously worked in the same repository and still works when run locally.

To Reproduce
Steps to reproduce the behavior:

  1. Go to a GitHub Actions
  2. Open the Linux/Ubuntu test job.
  3. Find the step: Upload bundle analysis to Codecov.
  4. See error:
    • get-pre-signed-url failed after 3 attempts
    • Failed to get pre-signed URL, bad response: "404 - Not Found"

Expected behavior
Bundle analyzer upload should successfully retrieve a pre-signed URL and upload bundle stats, as it does locally.

Regression
Yes, this appears to be a regression.

  • Last known successful behavior: previously in this repo’s CI pipeline (historically passing).
  • Current behavior: CI fails in GitHub Actions, while local command still succeeds.

Screenshots
N/A (logs included in CI output).

Product Area
Bundle analysis

Versions

  • OS: linux (ubuntu-latest in GitHub Actions)
  • Git Host: GitHub
  • CI/CD: GitHub Actions
  • Uploader: @codecov/bundle-analyzer@2.0.1 (via npx)

CI link

  • CI link: https://github.com/Nick2bad4u/eslint-config-nick2bad4u/actions/runs/25696783853/job/75446951853
  • Relevant Codecov output:
    • Attempting to fetch get-pre-signed-url
    • retries x3
    • Failed to get pre-signed URL, bad response: "404 - Not Found"

Additional context

  • Local run succeeds:
    npx @codecov/bundle-analyzer ./dist --bundle-name=nick2bad4u/eslint-config-nick2bad4u
  • In CI, bundle upload was gated to Linux only.
  • As mitigation, CI was updated to:
    • add continue-on-error: true to avoid blocking the entire pipeline.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Linux/Ubuntu test job and its “Upload bundle analysis to Codecov” step, then compare the CI invocation with the locally successful npx command. Investigate the pre-signed URL 404 and the @codecov/bundle-analyzer@2.0.1 behavior in GitHub Actions. Done means bundle stats upload successfully in CI without relying on continue-on-error.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, node.js
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.