Repository navigation
fix: fork install docs, scripts and settings stop pointing at upstream - #24
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
 [Medium impact] The PR appears safe to merge within its stated scope. SummaryThis PR points install instructions and release links at the fork’s nightly builds.
No new actionable issues were found. Review was based on source inspection; tests and UI checks were not run. Reviews (2) · Last reviewed commit: "Point the new Linux install notes and RE..." · Reviewed by Greptile |
Upstream's Linux section promised ARM64 desktop downloads the fork does not publish, and the README's desktop app link still opened t3.codes. The fork test now also rejects t3.codes download links.
eyeveil
marked this pull request as ready for review
November 7, 2026 12:48
Collaborator
|
Note Written by Retargeted to |
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.
Why
The fork publishes only nightly builds, but its install docs, install script headers, and the desktop update-track switch still sent fork users to upstream installs, upstream releases, or a stable channel the fork doesn't have. #23 moved the release source to the fork. This covers what it left.
What changed
install.shandinstall.ps1headers give the fork's raw script URL withT3CODE_CHANNEL=nightly. Their errors no longer point att3.codes/downloadornpm install -g t3.README.mdanddocs/user/install.mdlink the fork's releases, label package managers as installing upstream, and say the fork ships Linux x86_64 only.FORK_HAS_UPDATE_TRACKS = falsein@t3tools/shared/forkhides the desktop update-track switch and its settings search entry. The switch took its target from upstream's npmt3, which fork releases don't have.docs/user/updating.mdexplains this.fork.test.tsfails if the README, install guide, or scripts mentiont3.codes/install,t3.codes/download, a baret3.codeslink, or upstream's releases page.Scope
npx t3 …strings, plusupdating.md'snpx t3@<client-version>line, pointing at upstream npm. Fixing them means rewording shared upstream UI, so they need their own change.Tradeoffs
npx t3still runs upstream, and the docs now say so. Publishing a fork npm package needs the maintainer's OK.Blast Radius
Docs and scripts change for fork users only. Hiding the switch also hides its "machines on the other track" review path for connected remote machines.
Verification
scripts/install.sh, run as its header says in an isolated home, installed0.1.8-nightly.20261106.100, andt3 --versionreported it. WithoutT3CODE_CHANNELit stops with "could not find a stable release".vp run check:changed fork/mainpasses, andfork.test.tspasses 9 of 9.install.shon Linux arm64, where it should fail with "no release archive" because the fork publishes none.Model and harness: Claude Opus 5.5 (implementation, update onto main, review) via Claude Code in T3 Code.