Repository navigation
fix(runtime): install T3 Code from GitHub release archives - #46
Merged
Merged
Conversation
0libote
marked this pull request as ready for review
October 19, 2026 10:01
Check capacity before requesting and writing archives, reserve room for the running server, and recheck bounded batches and extraction. Cancel failed downloads, reject inconsistent sizes, and keep existing runtime state intact. Show release check failures persistently in Setup. Add disk-pressure regressions and responsive browser coverage for rate limits, checksums, escaped diagnostics, and recovery.
Use the existing CI token only for GitHub API requests, pass it through stdin instead of command arguments, and retry bounded transient metadata failures. Keep registry lookups unauthenticated and real version drift blocking. Retain pin-check output in smoke diagnostics. Add regressions for token isolation, public lookups, unavailable metadata and stale or invalid releases.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue: Updates are stuck at
0.1.1-nightly.20261016.3190because upstream stopped publishing the npm platform packages this container uses.Fix: Install and update T3 Code from official GitHub CLI archives, with SHA-256 verification. Image builds and Setup share the same implementation, preserving compatibility checks, database snapshots, rollback and existing cached runtimes.
Existing containers need a rebuilt image to receive the new updater.
Validation
Finishing validation
Reserve disk headroom before downloading, recheck during streaming and before extraction, and cancel and remove failed staging. Seven new regressions cover low space, preserved live state, unknown or inconsistent sizes, cancellation and cleanup.
Keep release-check failures visible in the existing Setup warning, including GitHub rate limits and missing checksums. Diagnostics render as text and clear after recovery.
The responsive update audit passed all 12 configurations, including light/dark, mobile, desktop and embedded layouts.
Real ARM64 nightly
0.1.1-nightly.20261020.3411passed checksum, Setup bridge, launcher compatibility and native authentication staging checks in a disposable home.Version pins and changed shell/syntax checks passed. Native image CI passed on
fad17f6for core and browser on amd64 and arm64, including the native archive, UI, smoke and amd64 lifecycle checks.Pin lookups use the existing CI token only for GitHub metadata, keep it out of command arguments and logs, retry bounded transient failures, and preserve lookup output in smoke diagnostics. Four additional tests cover token isolation, anonymous access, unavailable metadata and genuine version drift.