Repository navigation
docs(readme): name the DSH line the adapter targets - #8
Merged
Merged
Conversation
The test-coverage note still said "DSH 0.1.5"; the harness API line this adapter is written against is dsh-v0.1.7-alpha.1. Also states explicitly that the repository depends on no @deepseek-ai/dsh-* package, so the note describes the targeted host API surface rather than a dependency pin. Verified before opening this pull request: `npm test` -> 35 files / 435 tests passed. Docs only: no code, no dependency, no behaviour change.
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
2 participants
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.
What this changes
Two lines in
README.md, documentation only:DSH 0.1.5 适配. The harness API line this adapter is writtenagainst is now
dsh-v0.1.7-alpha.1, so the note is updated to match.being precise about — noting that this repository depends on no
@deepseek-ai/dsh-*package at all. The line therefore describes the host API surface the adapter targets, not a
dependency pin.
Why it is safe to merge
npm test→ 35 files / 435 tests passed on the branch base.package.jsondependency and peer-dependency sets are empty, which is exactly why theREADME wording matters: nothing in the manifest pins a harness version, so the README is the
only place a reader can learn which host line this adapter was written for.
Scope note
I deliberately did not touch anything else — no formatting sweep, no reorganisation, no
badges. If you would rather phrase the version sentence differently, or drop it entirely and keep
only the
0.1.5→0.1.7-alpha.1correction, say so and I will revise: that one-line correctionis the substance of this PR and the sentence is only there to make the claim explicit.