[Bug]: t3 update release checks ignore GitHub tokens

Open Beginner friendly
#12,852 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github, typescript
Domain
ci-cd, release, tooling

Research direction

Start by locating the updater code that sends GET /repos/pingdotgg/t3code/releases and produces “Could not list t3 releases.” Check how release requests are assembled, then verify that GH_TOKEN and GITHUB_TOKEN are considered in the stated order and sent as bearer authentication when available. Done means t3 update can use an available token while retaining the existing release-list behavior.

Written by the indexing model from the issue text.

Description

bug via-triage

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

Build, CI, or release tooling

Steps to reproduce

  1. Install a nightly or preview CLI release.
  2. Export a valid GH_TOKEN or GITHUB_TOKEN, or authenticate with gh auth login.
  3. Run t3 update from a network whose shared unauthenticated GitHub API quota is exhausted.

Expected behavior

t3 update should use an available GitHub token when it lists releases, so the request uses the authenticated API quota.

Actual behavior

The updater sends only the Accept header to GET /repos/pingdotgg/t3code/releases. It ignores GH_TOKEN and GITHUB_TOKEN, so every check uses GitHub's shared unauthenticated quota and can fail with Could not list t3 releases.

The update code may walk up to 10 pages because stable, preview, and nightly releases share one release list. This makes the unauthenticated limit easier to hit behind a shared egress IP.

Impact

Major degradation or frequent failure

Version or commit

0.0.43-nightly.20260920.2031; reproduced in source at origin/main (9ea9c3d5d)

Environment

Linux x64, shared corporate network

Workaround

npm install -g t3@nightly avoids the GitHub release-index request. A focused fix is to read GH_TOKEN, then GITHUB_TOKEN, and send Authorization: Bearer <token> when either is set.

Dominant language
TypeScript
Stars
23.2k
Forks
5.9k
Avg merge
10h 57m
Merged PRs (30d)
365

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.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.