Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
df2fa0f54b | ||
|
|
1f42d2a821 | ||
|
|
269360a4ea |
No files matched your search
@@ -2,6 +2,13 @@
|
||||
|
||||
Every release, newest first, generated from the commits in each release.
|
||||
|
||||
## v0.1.2 — 2026-09-26
|
||||
|
||||
### Documented
|
||||
|
||||
- lead the install instructions with the published git spec
|
||||
|
||||
|
||||
## v0.1.1 — 2026-09-26
|
||||
|
||||
### Fixed
|
||||
|
||||
@@ -49,6 +49,22 @@ about a millisecond; the only per-query network cost is one embedding call.
|
||||
|
||||
## Install
|
||||
|
||||
```sh
|
||||
dsh plugin --profile web add git+https://git.notexpectedyet.com/Not-Expected-Yet/dsh-recall.git
|
||||
```
|
||||
|
||||
That form installs whatever the default branch holds, pinned to a commit in the
|
||||
profile's lockfile. The semver fragment installs the newest release tag instead,
|
||||
and is what makes `dsh plugin update` follow releases — see
|
||||
[Releases](#releases) for the tag and versioning rules:
|
||||
|
||||
```sh
|
||||
dsh plugin --profile web add 'git+https://git.notexpectedyet.com/Not-Expected-Yet/dsh-recall.git#semver:^0.1.0'
|
||||
```
|
||||
|
||||
To run your own copy instead, add the directory — that becomes a `link:`
|
||||
dependency which tracks the working tree, so an edit needs no reinstall:
|
||||
|
||||
```sh
|
||||
dsh plugin --profile web add /path/to/dsh-recall
|
||||
```
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "dsh-recall",
|
||||
"version": "0.1.1",
|
||||
"version": "0.1.2",
|
||||
"private": true,
|
||||
"type": "module",
|
||||
"description": "Local-embedding code recall for DeepSeek Harness — returns ranked excerpts with line ranges instead of whole files, so the context window stops growing with every read.",
|
||||
|
||||
Reference in new issue
Block a user