docs(release): add install + dual-binary template to GitHub Release page#275
Merged
Merged
Conversation
Closes #265. The Release page used the auto-generated commit-title body. New users hitting the Release page from Twitter / npm-search had no on-page guidance that the dispatcher (`deepseek`) and the TUI runtime (`deepseek-tui`) ship as two binaries that must coexist; #258 was an external user spending 11 minutes figuring this out and #272 was the follow-on confusion. The new body covers: - npm wrapper as the recommended install - `cargo install deepseek-tui-cli deepseek-tui --locked` (both crates) - Manual download with a per-platform table showing both artifacts - sha256 verify using the existing `deepseek-artifacts-sha256.txt` - Changelog link
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a curated GitHub Release body template to the release workflow so the Release page documents how to install DeepSeek-TUI (including the dual-binary requirement) instead of relying on auto-generated notes.
Changes:
- Adds an “Install” section covering npm (recommended), Cargo, and manual per-platform downloads.
- Documents checksum verification using the existing
deepseek-artifacts-sha256.txtmanifest. - Adds a Release-page pointer to
CHANGELOG.md.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Cargo (Linux / macOS) | ||
|
|
||
| ```bash | ||
| cargo install deepseek-tui-cli deepseek-tui --locked |
Comment on lines
+152
to
+153
| **Both** binaries below must be downloaded for your platform and dropped into the same directory (e.g. `~/.local/bin/`): | ||
|
|
| | macOS ARM | `deepseek-macos-arm64` | `deepseek-tui-macos-arm64` | | ||
| | Windows x64 | `deepseek-windows-x64.exe` | `deepseek-tui-windows-x64.exe` | | ||
|
|
||
| Then `chmod +x` both (Unix) and run `./deepseek`. |
|
|
||
| ## Changelog | ||
|
|
||
| See [CHANGELOG.md](https://github.com/Hmbown/DeepSeek-TUI/blob/main/CHANGELOG.md) for the full notes for this release. |
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
Closes #265.
The Release page currently uses the auto-generated commit-title body. Adds a curated body template to the existing `softprops/action-gh-release@v1` step covering:
The cargo line lists both crates rather than `cargo install deepseek`. The meta-crate work in #264 turns out to have a workspace-build collision (commented on the issue with the trade-offs); when that lands, this body just needs a one-line update.
Test plan
🤖 Generated with Claude Code