Conversation
xiwangly2
marked this pull request as draft
September 26, 2026 06:39
Contributor
Author
|
追加了一轮 Java/包管理器架构边界修正:
验证:
|
Contributor
Author
|
追加更新:已继续收敛 x64-only 游戏部署路径,当前 Draft PR 分支更新到 本次新增:
验证:
|
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.
Summary
linux-riscv64package target and release artifact wiring.unzip/zip/7ztools instead of unavailable bundled native assets.Validation
npm run package:linux:riscv64:no-zipcd server && npm test -- --runTestsByPath src/__tests__/7z-extract-compress.test.ts src/__tests__/7z-binary-name.test.ts src/__tests__/7z-property.test.ts10.31.0.225,riscv64): installed distro Node.js 20.18.0 plus zip/7z tools, started the generatedlinux-riscv64package on port 39031, and verified the web UI returned HTML over HTTP. Logs showed expected PTY degradation and system ZIP/7z fallback.Notes
Docker is intentionally left at amd64/arm64 because the current Dockerfile still depends on architecture-specific SteamCMD, Java, PTY, ZipTools, and 7z assumptions that are not ready for riscv64.