Before submitting
Area
Build, CI, or release tooling
Steps to reproduce
- Open the app
- Switch to the "Nightly" update track
- Click check for update
Expected behavior
The expected behavior is that the nightly build is downloaded, and the user is allowed to update.
Actual behavior
The actual behavior is that the button switches to "Checking..." and then goes back to "Check for updates". The stable channel works properly for me. I received two different errors in my logs for this, which is interesting too, see below. The second one is probably just a github downtime issue or something but thought I'd include it.
Impact
Major degradation or frequent failure
Version or commit
0.0.20
Environment
Windows, Desktop version, Node v24.14.1, Bun 1.3.11
Logs or stack traces
# I received two different errors after trying this a couple of times
[2026-04-18T18:00:28.041Z] [stdout run=<redacted-run-id>] [desktop-updater] Checking for updates (web-ui)...
[2026-04-18T18:00:28.042Z] [stdout run=<redacted-run-id>] Checking for update
[2026-04-18T18:00:28.044Z] [stdout run=<redacted-run-id>] [desktop-updater] Looking for updates...
[2026-04-18T18:00:28.217Z] [stderr run=<redacted-run-id>] Error: Error: No published versions on GitHub
at newError (C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\node_modules\builder-util-runtime\out\error.js:5:19)
at GitHubProvider.getLatestVersion (C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\node_modules\electron-updater\out\providers\GitHubProvider.js:100:55)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async NsisUpdater.getUpdateInfoAndProvider (C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:389:19)
at async NsisUpdater.doCheckForUpdates (C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:402:24)
at async checkForUpdates (C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\apps\desktop\dist-electron\main.js:5111:3)
at async C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\apps\desktop\dist-electron\main.js:5615:13
at async Session.<anonymous> (node:electron/js2c/browser_init:2:116443)
[2026-04-18T18:00:28.219Z] [stderr run=<redacted-run-id>] [desktop-updater] Updater error: No published versions on GitHub
[2026-04-18T18:00:28.220Z] [stderr run=<redacted-run-id>] [desktop-updater] Failed to check for updates: No published versions on GitHub
# Second (probably not a real issue) error
[2026-04-18T18:04:38.101Z] [stdout run=<redacted-run-id>] [desktop-updater] Checking for updates (web-ui)...
[2026-04-18T18:04:38.102Z] [stdout run=<redacted-run-id>] Checking for update
[2026-04-18T18:04:38.104Z] [stdout run=<redacted-run-id>] [desktop-updater] Looking for updates...
[2026-04-18T18:04:49.202Z] [stderr run=<redacted-run-id>] Error: HttpError: 504
"method: GET url: https://github.com/pingdotgg/t3code/releases.atom\n\n Data:\n <html><body><h1>504 Gateway Time-out</h1>\nThe server didn't respond in time.\n</body></html>\n\n "
Headers: {
"cache-control": "no-cache",
"content-length": "92",
"content-type": "text/html",
"date": "Sat, 18 Apr 2026 18:04:48 GMT",
"strict-transport-security": "max-age=31536000; includeSubDomains; preload",
"x-frame-options": "DENY",
"x-github-request-id": "<redacted>",
"set-cookie": [
"_gh_sess=<redacted>; path=/; HttpOnly; secure; SameSite=Lax",
"_octo=<redacted>; expires=<redacted>; domain=.github.com; path=/; secure; SameSite=Lax",
"logged_in=no; expires=<redacted>; domain=.github.com; path=/; HttpOnly; secure; SameSite=Lax"
]
}
at createHttpError (C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\node_modules\builder-util-runtime\out\httpExecutor.js:21:12)
at IncomingMessage.<anonymous> (C:\Users\<redacted>\AppData\Local\Programs\t3-code-desktop\resources\app.asar\node_modules\builder-util-runtime\out\httpExecutor.js:152:28)
at IncomingMessage.emit (node:events:508:28)
at endReadableNT (node:internal/streams/readable:1701:12)
at process.processTicksAndRejections (node:internal/process/task_queues:89:21)
[2026-04-18T18:04:49.203Z] [stderr run=<redacted-run-id>] [desktop-updater] Updater error: 504
"method: GET url: https://github.com/pingdotgg/t3code/releases.atom\n\n Data:\n <html><body><h1>504 Gateway Time-out</h1>\nThe server didn't respond in time.\n</body></html>\n\n "
Headers: {
"cache-control": "no-cache",
"content-length": "92",
"content-type": "text/html",
"date": "Sat, 18 Apr 2026 18:04:48 GMT",
"strict-transport-security": "max-age=31536000; includeSubDomains; preload",
"x-frame-options": "DENY",
"x-github-request-id": "<redacted>",
"set-cookie": [
"_gh_sess=<redacted>; path=/; HttpOnly; secure; SameSite=Lax",
"_octo=<redacted>; expires=<redacted>; domain=.github.com; path=/; secure; SameSite=Lax",
"logged_in=no; expires=<redacted>; domain=.github.com; path=/; HttpOnly; secure; SameSite=Lax"
]
}
[2026-04-18T18:04:49.204Z] [stderr run=<redacted-run-id>] [desktop-updater] Failed to check for updates: 504
"method: GET url: https://github.com/pingdotgg/t3code/releases.atom\n\n Data:\n <html><body><h1>504 Gateway Time-out</h1>\nThe server didn't respond in time.\n</body></html>\n\n "
Headers: {
"cache-control": "no-cache",
"content-length": "92",
"content-type": "text/html",
"date": "Sat, 18 Apr 2026 18:04:48 GMT",
"strict-transport-security": "max-age=31536000; includeSubDomains; preload",
"x-frame-options": "DENY",
"x-github-request-id": "<redacted>",
"set-cookie": [
"_gh_sess=<redacted>; path=/; HttpOnly; secure; SameSite=Lax",
"_octo=<redacted>; expires=<redacted>; domain=.github.com; path=/; secure; SameSite=Lax",
"logged_in=no; expires=<redacted>; domain=.github.com; path=/; HttpOnly; secure; SameSite=Lax"
]
}Screenshots, recordings, or supporting files
No response
Workaround
I'm sure there's a way to just manually install the nightly version from this repo and build it locally.
Before submitting
Area
Build, CI, or release tooling
Steps to reproduce
Expected behavior
The expected behavior is that the nightly build is downloaded, and the user is allowed to update.
Actual behavior
The actual behavior is that the button switches to "Checking..." and then goes back to "Check for updates". The stable channel works properly for me. I received two different errors in my logs for this, which is interesting too, see below. The second one is probably just a github downtime issue or something but thought I'd include it.
Impact
Major degradation or frequent failure
Version or commit
0.0.20
Environment
Windows, Desktop version, Node v24.14.1, Bun 1.3.11
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
I'm sure there's a way to just manually install the nightly version from this repo and build it locally.