Skip to content

fix(install): expect fusion-code-<os>-<arch> name inside tarball - #278

Merged
dahai80 merged 1 commit into
mainfrom
fix/install-inner-name
Nov 17, 2026
Merged

dahai80 merged 1 commit into
mainfrom
fix/install-inner-name

Conversation

@dahai80

@dahai80 dahai80 commented Nov 17, 2026

Copy link
Copy Markdown
Owner

Live v0.8.5 run got past the resume loop + sha256 check, then failed at extraction: package-release.sh ships the binary as fusion-code-<os>-<arch> at the archive root, while the installer expected plain fusion-code. Installer now looks up the platform-suffixed name and installs it as fusion-code. README_CN gains the one-line install section.

Verified via stub-release e2e with the real archive layout (darwin-arm64 asset on a darwin-arm64 host): extract, rename, install, --version green.

package-release.sh ships the binary as fusion-code-<os>-<arch> at the
archive root (not fusion-code) — the live v0.8.5 run passed checksum
and failed at extraction with 'unexpected tarball layout'. Renames to
plain fusion-code on install. README_CN gains the one-line install
section.
@dahai80
dahai80 merged commit af340e3 into main Nov 17, 2026
2 checks passed
@dahai80
dahai80 deleted the fix/install-inner-name branch November 17, 2026 04:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant