Skip to content

e2e-upload on main fails: GitHub credential for the test user is invalid (401) #1321

Closed

Description

@neuromechanist

The Tests run on main for the v0.10.0 bump commit (run 34253738403) failed only in e2e-upload, which runs on pushes to main. Both cases fail the same way: the CLI's GitHub check prints "gh CLI error: gh: Bad credentials (HTTP 401)", so the GitHub token the job hands to gh (the test user's PAT in the repository secrets) is expired or revoked. Every other tier passed, and production is unaffected; this is a CI credential, not a release defect.

Fix: rotate the secret the e2e-upload job uses for gh (see .github/workflows/test.yml, the e2e-upload job's env), then re-run the job. Consider a nightly probe of that credential so it fails on a schedule rather than on a release day.

Activity

  1. neuromechanist commented on Sep 29, 2026

    @neuromechanist
    ContributorAuthor

    Fixed. GH_TOKEN was rotated on 2026-09-29 (classic PAT from nemarAdmin, repo and workflow scopes, 1-year expiry). Rerunning the failed job on the v0.10.8 strip commit (run 36522504540, attempt 2) turned e2e-upload green, and that Tests run on main now passes.

    To keep this from recurring silently, #1536 adds three things:

    • a token check at the start of e2e-upload, which fails in one labeled step naming the secret, its owner and the rotation command;
    • a daily credential-probe.yml that warns 30 days before expiry and fails the run at 14 days;
    • e2e-upload running on release PRs to main, so this shows up before a merge instead of after it.
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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions