@functional-systems/memdrive 0.1.0-rc.1 → 0.1.0

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 CHANGED
@@ -1,5 +1,15 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.0
4
+
5
+ First stable release of the standalone MemDrive SDK. The public API and storage
6
+ format are unchanged from 0.1.0-rc.1; the LambdaDB TypeScript client remains pinned
7
+ to 0.12.0.
8
+
9
+ - Provide memory storage, vector and hybrid retrieval, complete-original reads, metadata inspection, branches and portable agent tools.
10
+ - Wait for npm registry metadata to become visible after a successful publication, without retrying publication; verify archive identity and report channel state on reruns.
11
+ - Document stable installation and the `latest`, `rc` and `dev` channels.
12
+
3
13
  ## 0.1.0-rc.1
4
14
 
5
15
  First release candidate of the standalone MemDrive SDK, backed by the pinned
package/README.md CHANGED
@@ -8,15 +8,16 @@ LambdaDB client; the caller owns connection credentials and transport.
8
8
 
9
9
  The package is `@functional-systems/memdrive`, licensed under Apache-2.0.
10
10
  It builds ESM and CommonJS with TypeScript declarations and supports Node.js
11
- 20.12+ and browser bundlers. Install this release candidate and the LambdaDB client
11
+ 20.12+ and browser bundlers. Install this stable release and the LambdaDB client
12
12
  used to initialize it:
13
13
 
14
14
  ```sh
15
- npm install @functional-systems/memdrive@0.1.0-rc.1 @functional-systems/lambdadb@0.12.0
15
+ npm install @functional-systems/memdrive@0.1.0 @functional-systems/lambdadb@0.12.0
16
16
  ```
17
17
 
18
- Release candidates may change before a stable release. Use `@rc` to follow release
19
- candidates, `@dev` for development builds, or an exact version for reproducibility.
18
+ An unqualified install follows the stable `latest` channel. Use `@rc` to follow
19
+ release candidates, `@dev` for development builds, or an exact version for
20
+ reproducibility.
20
21
  To build locally, run `npm ci`, `npm run build`, and `npm pack`, then install the
21
22
  resulting tarball in the consumer project. See [CONTRIBUTING.md](CONTRIBUTING.md)
22
23
  for development and
@@ -171,8 +172,7 @@ Recalls share a default concurrency bound of five across branch views; the
171
172
  caller may configure it. Batch request count is not artificially capped by the
172
173
  SDK; a hosted MCP wrapper can impose its own exposed tool limit.
173
174
 
174
- The development format stays `mems-v0` until release. Recreate disposable stores
175
- after incompatible layout changes. MemDrive uses LambdaDB SDK 0.12.0. Build
175
+ The storage format is `mems-v0`. MemDrive uses LambdaDB SDK 0.12.0. Build
176
176
  artifacts are generated with `npm run build`; browser applications bundle the
177
177
  public package entry point with their own build tools.
178
178
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@functional-systems/memdrive",
3
- "version": "0.1.0-rc.1",
3
+ "version": "0.1.0",
4
4
  "description": "Source-linked memory storage and retrieval backed by LambdaDB.",
5
5
  "type": "module",
6
6
  "engines": {
@@ -97,5 +97,5 @@
97
97
  "publishConfig": {
98
98
  "access": "public"
99
99
  },
100
- "memdriveSourceCommit": "238c57aa30f8c7c0e67a11e71879b9eff1249f50"
100
+ "memdriveSourceCommit": "6162838e7f48627d1d108000c7a420bef1b26b3e"
101
101
  }