Update DeepSeek Harness: Version Pins and Rollback Checklist
Treat a preview upgrade as a small migration. Record the currently working package version, preserve its configuration, and test the candidate with the same basic task. npm latest, npm next and the Python SDK are separate release channels, so matching-looking numbers are not a compatibility guarantee.
Sharing includes the public link only, without local progress or private configuration.
Capture a useful baseline
Save the exact package version, Node version, profile name and expected outcome of one small task. Consult the latest-version page for registry identities; the historical rc.7 runtime record is not a test of today’s release.
Test a pinned candidate
Use npx @deepseek-ai/dsh@VERSION web with a reviewed exact version. A moving dist-tag can resolve differently on the next run. Read the official release notes and configuration changes before reusing a profile.
- Back up the profile and credential files securely.
- Do not copy secrets into an issue or shared checklist.
- Check Web UI startup, model selection and one small request separately.
Keep rollback explicit
If the test fails, preserve the sanitized failure evidence and return to your recorded version with its compatible configuration. Reinstalling an older package alone may not reverse a configuration migration.
- Stop the candidate instance before relaunching.
- Restore only from the backup you identified.
- Compare the same baseline task before resuming regular work.
First-party sources
Open the pinned or retrieved source before acting on a changed release candidate.
- Official docs/user/guide/providers.mdOfficial documentation · retrieved 2026-10-04↗
- Official apps/cli/reference/README.mdOfficial documentation · retrieved 2026-10-04↗
- Official packages/llm/llm-deepseek/README.mdOfficial documentation · retrieved 2026-10-04↗
- Official packages/llm/llm-pi-ai/README.mdOfficial documentation · retrieved 2026-10-04↗