02 / IT · Analysis
Qwen Code SDK 0.1.29 reaches GitHub after a workflow failure
Fixes to long-session caching and a memory setting sit under bundled CLI entries, where the SDK number alone does not show them.

Qwen Code SDK 0.1.29 for TypeScript, which bundles version 0.26.9 of the command-line tool (CLI), went out on npm, the JavaScript package registry, before its GitHub release was backfilled on 9 Nov 2026, the release note said. The original workflow failed at the release-branch push step, after npm publication.
The note lists the bundled CLI number separately from the SDK number in each entry, and it also carries entries for earlier CLI versions. Fixes that change behaviour sit under those CLI entries, so the SDK number alone does not reveal them.
The first change to read in the note is where the CLI is built from. Cache behaviour in long sessions, a memory setting and the history of the backfill follow.
The CLI builds from the same source as the SDK
The release note gives the origin of the CLI bundled with this SDK as "CLI built from source". An explanation in brackets says the build used the same branch and ref as the SDK.
Entries up to CLI 0.23.0 in the same note list the latest stable CLI on npm as the origin. Every entry from CLI 0.23.1 onwards lists a source build. The note does not explain the switch.
Long sessions keep their prompt cache
The CLI 0.23.0 entry records a fix to microcompaction, the step that clears old tool results once a size threshold is passed. The step now clears results toward a low watermark, a lower threshold (#8464).
Before the fix, the step rewrote a different part of the start of the conversation on every later turn. The note said that behaviour is gone, so long, tool-heavy sessions reuse the prompt cache, stored input that a model provider can process again at lower cost, and cached-input cost falls. It did not give the size of the saving.
Turning off auto memory also removes its instructions
Another fix in the CLI 0.23.0 entry concerns the memory.enableManagedAutoMemory setting. According to the note, the availability of managed memory now follows that setting (#6941).
Hosts that turn off automatic memory no longer have remember and dream requests admitted, the note said. The managed-memory instructions also drop out of the system prompt. Local patches applied to prevent this problem can be removed.
Npm packages that shipped ahead of their GitHub records
The release note cites #16490 as the reference for the 0.1.29 backfill. The 0.1.5 entry in the same note is also a backfill of an npm-published version. On that occasion the workflow failed before the GitHub release was created.
The note does not give the cause of the latest push failure. In both cases npm publication came before the GitHub release record. For developers who track SDK changes through GitHub releases alone, that lag is a gap in the record.