Repository navigation
fix(release): fork installs update from the fork's releases - #9
Closed
ScriptedAlchemy wants to merge 3 commits into
Closed
ScriptedAlchemy wants to merge 3 commits into
ScriptedAlchemy wants to merge 3 commits into
Conversation
Fork builds used a -preview version, which ships no update feed, so installs never updated. They now use a -fork version on the stable channel, so the build writes a GitHub feed for GITHUB_REPOSITORY (this fork) and the release carries latest*.yml manifests and blockmaps. Tags drop the fork- prefix so the app's release links resolve, and signing secrets pass through when configured. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
t3 update, remote server update checks, and pinned runtime downloads read releases from upstream. They now read this fork's releases, and the fork release publishes the SHA256SUMS file those downloads are verified against. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream moved Windows packaging to Linux runners with a separate Windows verify job. The fork still packaged on windows-2025, where tsdown's Node extraction picks up Git Bash's GNU tar and fails, so every fork release since 2026-10-20 failed before publishing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ScriptedAlchemy
changed the title
Owner
Author
|
Closing: macOS update installs need a signed app (Squirrel.Mac checks the code signature), and the fork has no Apple signing set up. |
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.
Fork installs never updated from the fork. Desktop builds were versioned
-preview, which ships no update feed.t3 updateread upstream's releases. And no fork release has been published since 2026-10-20, because the Windows job fails every run.Desktop updates (
fork-release.yml)-fork.YYYYMMDD.Non the stable channel. The build writes aprovider: githubfeed forGITHUB_REPOSITORY, which is this fork, so installs checkScriptedAlchemy/t3code's latest release and never upstream's.latest-mac.yml,latest-linux.yml,latest.yml(renamed back from the per-archlatest-win-x64.yml) and the blockmaps.v<version>instead offork-v<version>, so the app's "view release" link resolves.secrets: inheritpasses signing secrets through once they're configured.scripts/build-desktop-artifact.test.tschecks that a-forkversion gets a stable GitHub feed for the repository that built it.t3 updatepackages/shared/src/cliRelease.tsnow reads releases from the fork. This coverst3 update, the mobile app's server-update check, and pinned runtime downloads.SHA256SUMSfile those downloads are verified against.Release failures
windows-2025. There, tsdown extracts its Node zip with the firsttaron PATH, which is Git Bash's GNU tar, and it fails withtar: Cannot connect to C: resolve failed.ubuntu-24.04withverify_runner: windows-2025.Caveats
release-desktop.ymlreads. Windows and Linux AppImage install unsigned updates.-previewinstalls have no feed. Each one needs one manual install of a new-forkrelease.main, so this PR's CI does not exercise them.🤖 Generated with Claude Code (Claude Opus 5.5)