@theokit/memory-supermemory 2.0.0 → 3.0.2
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/CHANGELOG.md +43 -0
- package/package.json +8 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,48 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.0.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- a3ae640: Declare `repository` so these packages can publish with provenance.
|
|
8
|
+
|
|
9
|
+
npm cross-checks a manifest's `repository.url` against the repository recorded in the signed
|
|
10
|
+
provenance statement, and an empty value cannot match — the PUT is refused with E422 after the
|
|
11
|
+
statement has been signed and written to the public transparency log. Six of the twelve publishable
|
|
12
|
+
packages carried an empty field; it went unnoticed because nothing needed it until provenance was
|
|
13
|
+
enabled, and because each package publishes independently, so the release run went red while the
|
|
14
|
+
package everyone was watching succeeded.
|
|
15
|
+
|
|
16
|
+
`directory` is set alongside the URL, so the registry links to each package rather than to the
|
|
17
|
+
repository root.
|
|
18
|
+
|
|
19
|
+
## 3.0.1
|
|
20
|
+
|
|
21
|
+
### Patch Changes
|
|
22
|
+
|
|
23
|
+
- 8790f70: Refuse a `workspace:` range before it can reach npm.
|
|
24
|
+
|
|
25
|
+
Five of this repo's twelve publishable packages declare internal dependencies as `workspace:^`, which
|
|
26
|
+
is correct on disk and becomes an unrecoverable defect if the publish goes out through a tool that
|
|
27
|
+
does not rewrite it: `pnpm` resolves the protocol while packing, `npm` ships the manifest verbatim.
|
|
28
|
+
A version published that way fails to install for everyone and cannot be corrected — only
|
|
29
|
+
deprecated.
|
|
30
|
+
|
|
31
|
+
Every publishable package now runs the guard in `prepublishOnly`, so it fires whichever way the
|
|
32
|
+
publish is invoked, and `pnpm release` runs it once across the repo before `changeset publish`.
|
|
33
|
+
|
|
34
|
+
Note for anyone reading a published manifest: the `prepublishOnly` entry points at a path inside
|
|
35
|
+
this repository. It never runs for a consumer — the hook only fires when the package itself is
|
|
36
|
+
published — and guarding the entry point that a hand-run `npm publish` actually uses was worth the
|
|
37
|
+
cosmetic wart of shipping the line.
|
|
38
|
+
|
|
39
|
+
## 3.0.0
|
|
40
|
+
|
|
41
|
+
### Patch Changes
|
|
42
|
+
|
|
43
|
+
- Updated dependencies
|
|
44
|
+
- @theokit/sdk@4.0.0
|
|
45
|
+
|
|
3
46
|
## 2.0.0
|
|
4
47
|
|
|
5
48
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@theokit/memory-supermemory",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "3.0.2",
|
|
4
4
|
"description": "Supermemory memory adapter for @theokit/sdk — wraps supermemory@^4 with the MemoryAdapter contract (ADR D141).",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"type": "module",
|
|
@@ -30,14 +30,19 @@
|
|
|
30
30
|
],
|
|
31
31
|
"peerDependencies": {
|
|
32
32
|
"supermemory": "^4.21.0",
|
|
33
|
-
"@theokit/sdk": "^
|
|
33
|
+
"@theokit/sdk": "^4.43.0"
|
|
34
34
|
},
|
|
35
35
|
"devDependencies": {
|
|
36
36
|
"supermemory": "^4.21.1",
|
|
37
37
|
"tsup": "^8.5.0",
|
|
38
38
|
"typescript": "^5.8.0",
|
|
39
39
|
"vitest": "^4.1.8",
|
|
40
|
-
"@theokit/sdk": "
|
|
40
|
+
"@theokit/sdk": "4.43.0"
|
|
41
|
+
},
|
|
42
|
+
"repository": {
|
|
43
|
+
"type": "git",
|
|
44
|
+
"url": "git+https://github.com/usetheodev/theokit-sdk.git",
|
|
45
|
+
"directory": "packages/memory-supermemory"
|
|
41
46
|
},
|
|
42
47
|
"scripts": {
|
|
43
48
|
"build": "tsup",
|