Skip to content

[Bug Report] Bitbucket organization private repositories stopped to work #926

Open

Description

@ScarletKuro

Describe the bug
Since April 20, 2026, private repositories have stopped working.

Initially, logging in via Bitbucket was failing. it either caused an infinite redirect or returned a 500 error. Eventually, login started working again, but private repositories within organizations are no longer visible.

I can still see my personal private repositories, but organization private repositories do not appear. Public repositories are visible as expected.

The "Sync" button does not trigger any action.

When I try to open a repository directly (e.g., https://app.codecov.io/bb/tallink/central-config-server), I get the following error:

Not found

To view private repositories ensure you are logged in, you can also check on Codecov's status:
https://status.codecov.io/
or see our docs:
https://docs.codecov.io/

Error 404

I am a member of the organization, and network requests confirm that the API recognizes my membership in "tallink".

I also tested with other organizations I belong to, and the issue persists across all of them.

Expected behavior
Private repositories to show up in https://app.codecov.io/bb/{org_name}

Screenshots

Image Image

Additional context
Add any other context about the problem here.

Activity

  1. linear commented on Apr 22, 2026

    @linear
  2. ownede commented on Apr 22, 2026

    @ownede

    Having the same issue, can't access my repos from codecov, I also don't see PR comments being added while submitting the changes via CI.

  3. konstantin-nesterov commented on Apr 22, 2026

    @konstantin-nesterov

    We are seeing the same symptom on our Bitbucket workspace since ~Apr 22, 2026 — every repository returns 404 in the UI, "Sync" does nothing, PR comments stop showing up. Dropping some extra evidence that points at a likely root cause, in case it helps.

    What we see on the API side

    Using a workspace-level Codecov API token, probing Codecov's REST v2 directly:

    GET /api/v2/bb/workspace/repos/?active=true
    → { "count": 0 }
    
    GET /api/v2/bb/workspace/repos/?page_size=5
    → { "count": 3, "results": [ "cloud-cost-service", "bri-12-test2", "r360" ] }
       (expected: dozens; what's left looks like stale entries)
    
    GET /api/v2/bb/workspace/repos/<repo>/
    → HTTP 410
      { "detail": "Bitbucket API: Gone" }      ← this is the smoking gun
    
    GET /api/v2/bb/workspace/repos/<repo>/commits/
    → results: null
    
    GET /api/v2/bb/workspace/          → HTTP 200 (workspace object still cached)
    GET /api/v2/bb/workspace/users/    → count: 310 (user list still cached)

    Coverage uploads keep returning HTTP 200, so data still reaches Codecov — it just isn't surfaced anywhere.

    Our hypothesis: Atlassian CHANGE-2770

    HTTP 410 with a payload of "Bitbucket API: Gone" is exactly what Bitbucket Cloud started returning for the cross-workspace REST APIs, whose final removal landed on Apr 14, 2026:

    Other integrators had to migrate off the same endpoints — e.g. Renovate (renovatebot/renovate#42102) and GitLab (https://gitlab.com/gitlab-org/gitlab/-/issues/589153). The replacement is GET /2.0/user/workspaces + GET /2.0/repositories/{workspace} instead of GET /2.0/repositories?role=....

    Pattern of what's broken vs what still works matches this perfectly:

    Feature Uses the deprecated cross-workspace API? Observed
    Coverage upload (/upload/v4) No 200 OK
    Repo list / "Sync" for an org Yes empty / no-op
    Individual repo page / PR report Yes 410 → 404 in UI
    Users list, workspace object No (cached) still work
    Personal private repos No (owner-scoped) still work (matches OP)

    Heads-up: a second Atlassian change is coming May 4

    While on this topic — a related deprecation is rolling out now:

    • CHANGE-3052 (OAuth 2.0 and API authentication changes) — brownouts since Apr 20, 2026, final enforcement on May 4, 2026. Among other things: client_credentials grants no longer return a refresh_token, all token-authenticated requests must go to api.bitbucket.org (not www.bitbucket.org), and a few auth patterns stop being accepted.
    • Ref: https://developer.atlassian.com/cloud/bitbucket/changelog#CHANGE-3052

    If Codecov's Bitbucket OAuth flow still relies on any of those, we might get a second wave of breakage on May 4 — worth looking at together.

    Asks

    1. Can someone from Codecov confirm the Bitbucket adapter is hitting CHANGE-2770 and that a fix is underway?
    2. Any ETA would really help us communicate internally.
    3. Will coverage uploaded during the outage be re-attached to repos once the adapter is fixed, or should we plan to re-upload?

    Happy to run further diagnostic calls against our workspace if it helps narrow things down.

  4. ScarletKuro commented on Apr 22, 2026

    @ScarletKuro
    Author

    Hopping that maybe someone with Pro support can escalate this and point to to this issue?

  5. ScarletKuro commented on Apr 24, 2026

    @ScarletKuro
    Author

    Today at 8:00 UTC time I started to see private repos again, a hour ago it wasn't working.

  6. ownede commented on Apr 30, 2026

    @ownede

    As for today, Codecov posts comments to my BB repo, but I'm not able to see my repos on codecov ._.

  7. ScarletKuro commented on May 1, 2026

    @ScarletKuro
    Author

    Hmmm weird, I can see all my repos

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions