chore(release): bump version to 0.8.11 + CHANGELOG#678
Merged
Conversation
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
Contributor
There was a problem hiding this comment.
Pull request overview
Finalizes the v0.8.11 patch release by synchronizing version numbers across the Rust workspace crates and the npm wrapper, regenerating Cargo.lock, and adding a new 0.8.11 section to the changelog.
Changes:
- Bump workspace version to
0.8.11and update internal path-dependency version pins accordingly. - Bump
npm/deepseek-tuipackage version + default binary artifact version to0.8.11. - Add
CHANGELOG.mdentry for0.8.11and regenerateCargo.lock.
Reviewed changes
Copilot reviewed 12 out of 13 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| Cargo.toml | Bumps workspace package version to 0.8.11. |
| Cargo.lock | Regenerated to reflect 0.8.11 crate versions. |
| CHANGELOG.md | Adds 0.8.11 release notes section. |
| npm/deepseek-tui/package.json | Bumps npm wrapper version + deepseekBinaryVersion to 0.8.11. |
| crates/tui/Cargo.toml | Updates internal dependency pins to 0.8.11. |
| crates/tools/Cargo.toml | Updates internal dependency pin to 0.8.11. |
| crates/hooks/Cargo.toml | Updates internal dependency pin to 0.8.11. |
| crates/execpolicy/Cargo.toml | Updates internal dependency pin to 0.8.11. |
| crates/core/Cargo.toml | Updates internal dependency pins to 0.8.11. |
| crates/config/Cargo.toml | Updates internal dependency pin to 0.8.11. |
| crates/cli/Cargo.toml | Updates internal dependency pins to 0.8.11. |
| crates/app-server/Cargo.toml | Updates internal dependency pins to 0.8.11. |
| crates/agent/Cargo.toml | Updates internal dependency pin to 0.8.11. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+21
to
+22
| can re-enable it explicitly via `[compaction] enabled = true` in | ||
| `~/.deepseek/config.toml`. |
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), | ||
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
|
|
||
| ## [0.8.11] - 2026-05-04 |
7 tasks
Hmbown
force-pushed
the
chore/v0.8.11-release
branch
from
6da7db5 to
e608665
Compare
Final step in the v0.8.11 patch release. Bumps the workspace `Cargo.toml`, all 9 internal path-dep version pins, and `npm/deepseek-tui/package.json` to **0.8.11**. `Cargo.lock` regenerated alongside. The v0.8.11 CHANGELOG entry already landed on `main` via the cache-maxing overhaul PR (#684). This commit only stamps the version. Together they ship: * **Cache-maxing for V4 1M context** — engine no longer rebuilds the system prompt on every turn (#684's `Session::last_system_prompt_hash`), the volatile working-set summary moved out of the system prompt into per-turn `<turn_meta>` on the latest user message, the tool array is anchored with `cache_control: ephemeral`, and the `messages_with_turn_metadata` injection skips tool-result messages so the assistant→tool_result invariant stays intact. * **500K compaction floor** — automatic compaction refuses below 500K tokens via `MINIMUM_AUTO_COMPACTION_TOKENS`. Manual `/compact` bypasses (explicit user agency). * **Token-only compaction trigger** — dropped `CompactionConfig::message_threshold` and the message-count branch in `should_compact`; that 128K-era heuristic only fired on long sessions of small messages, exactly the case where rewriting the V4 prefix cache is most wasteful. * **Legacy 128K naming** — `DEFAULT_CONTEXT_WINDOW_TOKENS` → `LEGACY_DEEPSEEK_CONTEXT_WINDOW_TOKENS`. * **`npm install` resilience** — `install.js` now retries with exponential backoff, enforces per-attempt timeout + 30 s stall detector, honors `HTTPS_PROXY` / `HTTP_PROXY` / `NO_PROXY` (pure Node, no new dependencies), and prints download progress to stderr. Driven by a community report that `npm install` took 18 minutes through a CN npm mirror; the GitHub Releases binary fetch was the bottleneck and CN mirrors don't proxy GitHub. Verified locally: * cargo fmt --all -- --check ✓ * cargo clippy --workspace --all-targets --all-features --locked -- -D warnings ✓ * cargo test --workspace --all-features --locked ✓ * parity gates (snapshot, parity_protocol, parity_state) ✓ * bash scripts/release/check-versions.sh ✓ (workspace=0.8.11, npm=0.8.11, lockfile in sync) * node scripts/release/npm-wrapper-smoke.js ✓ Reminder for the maintainer at release time: the npm publish is manual and requires 2FA OTP on every publish. After this PR merges and the GitHub Release is fully drafted by `auto-tag.yml`, publish from a developer machine: cd npm/deepseek-tui npm publish --access public The `prepublishOnly` hook checks all eight binaries plus the SHA256 manifest are present on the GitHub Release before letting `npm publish` proceed, so this must happen *after* the GitHub Release is finalized. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Hmbown
force-pushed
the
chore/v0.8.11-release
branch
from
e608665 to
9366a7c
Compare
MMMarcinho
pushed a commit
to MMMarcinho/DeepSeek-TUI
that referenced
this pull request
May 6, 2026
chore(release): bump version to 0.8.11 + CHANGELOG
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
Final step in the v0.8.11 patch release. Bumps workspace
Cargo.toml, all 9 internal path-dep version pins, andnpm/deepseek-tui/package.jsonto 0.8.11.Cargo.lockregenerated alongside. New CHANGELOG section covers the merged PRs only.What landed in v0.8.11
doctorflags mismatchesreasoning_contentanchor pinnedRUST_LOG=deepseek_tui::compaction=debugshows framing fork + cache-hit denominatorview_stacktracingRUST_LOG=deepseek_tui::view_stack=debugshows push/pop kind + depth (diagnostic for rare sub-agent black-screen symptom)Test plan
cargo fmt --all -- --check— cleancargo clippy --workspace --all-targets --all-features --locked -- -D warnings— cleancargo test --workspace --all-features --locked— 2033 passed in TUI bin (2 ignored), all other crates greencargo test -p deepseek-tui-core --test snapshot --locked✓ /cargo test -p deepseek-protocol --test parity_protocol --locked✓ /cargo test -p deepseek-state --test parity_state --locked✓bash scripts/release/check-versions.sh—workspace=0.8.11, npm=0.8.11, lockfile in syncgit diff --exit-code -- Cargo.lock— staged only as part of this PR (regenerated for the bump)Release pipeline reminder
When this PR merges to
main,auto-tag.ymlwill create thev0.8.11tag usingRELEASE_TAG_PAT(assumed configured), which firesrelease.ymlto build the matrix, draft the GitHub Release, and upload the eight signed binaries plus the SHA256 manifest. Don't push the tag manually unlessauto-tagfalls back.The npm publish is manual because the npm account requires 2FA OTP on every publish. After the GitHub Release goes live, run from a developer machine:
The
prepublishOnlyhook checks all eight binaries plus the checksum manifest are present on the GitHub Release before lettingnpm publishproceed, so don't try to publish before the GitHub Release is finalized.