memcue-dsh 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -33,9 +33,9 @@ Node refuses to strip TypeScript types, so a `.ts` entry cannot be loaded from a
|
|
|
33
33
|
No `path:` parameter and no local directory are needed. From a local checkout, `dsh plugin add /path/to/memcue`
|
|
34
34
|
installs the same root package.
|
|
35
35
|
|
|
36
|
-
The plugin directory is also a standalone package
|
|
37
|
-
|
|
38
|
-
`dsh plugin add /path/to/memcue/plugins/deepseek-harness`.
|
|
36
|
+
The plugin directory is also a standalone package, published as
|
|
37
|
+
[`memcue-dsh`](https://www.npmjs.com/package/memcue-dsh). `dsh plugin add memcue-dsh` installs it without the
|
|
38
|
+
repository; a local checkout can use `dsh plugin add /path/to/memcue/plugins/deepseek-harness`.
|
|
39
39
|
|
|
40
40
|
The plugin manager adds the package to the profile's `dsh.profile.bundles`; the install dialog's **Enable now**
|
|
41
41
|
switches the bundle on. A repository install is a Git dependency, so a `git pull` reaches the next start without
|
|
@@ -105,6 +105,26 @@ The suite mounts the plugin against a plain object context and a stub binary, so
|
|
|
105
105
|
running harness — only a checkout where `@deepseek-ai/dsh-llm` and `@deepseek-ai/dsh-tools` resolve. It also checks
|
|
106
106
|
the bundle metadata and that the bundle patch points at the loadable ESM entry.
|
|
107
107
|
|
|
108
|
+
## Releasing
|
|
109
|
+
|
|
110
|
+
The standalone package is published as `memcue-dsh`.
|
|
111
|
+
|
|
112
|
+
CI publishes on a `dsh-v*` tag or by manual dispatch through `.github/workflows/publish-dsh.yml`. It uses npm
|
|
113
|
+
Trusted Publishing (OIDC): the workflow has `id-token: write`, no token, and no `NPM_TOKEN` secret. The trusted
|
|
114
|
+
publisher is configured for the `juev/memcue` repository and the `publish-dsh.yml` workflow, with direct publish and
|
|
115
|
+
stage-publish allowed.
|
|
116
|
+
|
|
117
|
+
A maintainer can still publish manually; npm asks for the 2FA code:
|
|
118
|
+
|
|
119
|
+
```sh
|
|
120
|
+
cd plugins/deepseek-harness
|
|
121
|
+
npm publish --access public
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
A fork needs its own trusted publisher, or a granular `NPM_TOKEN` on a `NODE_AUTH_TOKEN` environment variable. A
|
|
125
|
+
granular token without the 2FA bypass cannot run `npm publish`: use `npm stage publish` and approve the stage with
|
|
126
|
+
`npm stage approve <id>`.
|
|
127
|
+
|
|
108
128
|
## What differs from the Hermes plugin
|
|
109
129
|
|
|
110
130
|
- Hermes' `MEMORY.md` mirror and its four memory tools have no counterpart here: dsh has no built-in memory files, so
|