Repository navigation
fix: fork builds update from their own releases, and the update capsule keeps its label - #50
Merged
Merged
Conversation
…le keeps its label A server built in a fork asked upstream's releases for its fork-only version and got a 404 on SHA256SUMS, unless T3CODE_RELEASE_BASE_URL was set by hand on that machine. Server, desktop and web builds now bake in the repository they were built in (GITHUB_REPOSITORY, or T3CODE_DESKTOP_UPDATE_REPOSITORY), the same source the desktop updater already uses, so release lookups and archive downloads default to it. Builds without one still use upstream. In a narrow sidebar the update capsule had no room for its label beside the footer icons and showed only an off-center "Retry". It now wraps onto its own row above the icons when it cannot fit its label. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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.
Problem
A server built in a fork failed its update with
HTTP 404 from github.comwhile downloading the release checksums. It asked upstream's releases for a version that only this fork publishes, because the release source was hardcoded to upstream unlessT3CODE_RELEASE_BASE_URLwas set by hand on the machine.In a narrow sidebar the update capsule had no room for its label beside the footer icons, so a failed update showed only an off-center "Retry" in a red ring.
Fix
GITHUB_REPOSITORY, orT3CODE_DESKTOP_UPDATE_REPOSITORY), the source the desktop updater already uses. Release lookups, archive downloads and the SSH remote install default to it. Builds without one, and invalid values, still use upstream.T3CODE_RELEASE_BASE_URLand a managed mirror still win.@t3tools/shared/cliReleaseand is shared.C… Retrysqueezed beside four icons; after:Center failed · Retryon a full-width row). In a wide sidebar it stays inline.Verification
GITHUB_REPOSITORYset to this fork and rant3 update --channel nightlyinto an empty home with no release env set: it listed this fork's releases and installed the newest fork nightly, checksum verified.vp run check:changed: all pass except the React Compiler coverage test forDictationHistoryDialog.tsx, which fails the same way oncollin/mainand is not touched here.Claude Fable 5.2, Claude Code
🤖 Generated with Claude Code