@clinia/context-engine-js 0.5.0-rc.2 → 0.5.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 +26 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,31 @@
|
|
|
1
1
|
# @clinia/context-engine-js
|
|
2
2
|
|
|
3
|
+
## 0.5.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- db7bdab: **`@clinia/context-engine-js` is now published to the public npm registry.** Install it with `npm install @clinia/context-engine-js` — no registry configuration, no `.npmrc`, no authentication. Previously it existed only on GitHub Packages, so a clone outside the Clinia org could not install it at all.
|
|
8
|
+
|
|
9
|
+
Publishing continues to GitHub Packages as well, at the same version, so anything already resolving from there keeps working. The npm publish is the source of truth; the mirror is best-effort.
|
|
10
|
+
|
|
11
|
+
The package now declares `license: "Apache-2.0"` and ships a `LICENSE` file and its `CHANGELOG.md`. It carries no `repository` field on purpose: the source monorepo is private, so the link npm would render 404s for every consumer.
|
|
12
|
+
|
|
13
|
+
Two packaging defects are fixed while the consumer base is still small. `exports` listed the `import` condition before `types`, and there was no top-level `types` — so consumers on `moduleResolution: "node"` resolved the package with no type declarations at all. Both are corrected; the package remains ESM-only, which the README now states outright, since `require()` of it throws `ERR_REQUIRE_ESM`.
|
|
14
|
+
|
|
15
|
+
**`{ clientId, clientSecret }` is now a complete `auth` config.** The token endpoint and the RFC 8707 `resource` indicator default to Clinia's authorization server, so connecting to a workspace no longer means copying two console URLs into your code. `tokenUrl` and `issuer` still override it for a different authorization server, and `resource` is only defaulted when the endpoint is too — a third-party token endpoint never receives Clinia's resource value. Nothing breaks: every config that was valid before still means what it meant, and `tokenUrl` merely became optional.
|
|
16
|
+
|
|
17
|
+
- 405af06: **Renamed: `@clinia/patient-memory-js` is now `@clinia/context-engine-js`.**
|
|
18
|
+
|
|
19
|
+
To upgrade, change the dependency name and your imports, and rename two symbols:
|
|
20
|
+
- `PatientMemoryClient` → `ContextEngineClient`
|
|
21
|
+
- `PatientMemoryClientOptions` → `ContextEngineClientOptions`
|
|
22
|
+
|
|
23
|
+
Nothing else about the surface changed: same constructor options, same `http` client, same generated types and resource classes. Versions 0.4.0 and earlier remain published under the old name and are not being withdrawn, but no further versions will be released there.
|
|
24
|
+
|
|
25
|
+
The types are now generated from `openapi/context-engine.yaml`, which is the spec attached to each release under that name.
|
|
26
|
+
|
|
27
|
+
The retired name is also gone from everything the package ships, which the rename had missed: the `auth` module's doc comment (carried into `dist/auth.d.ts` and into the sourcemap's inlined source), and the README's `audience` example, `baseUrl` sample host, and options table. `CHANGELOG.md` still names `@clinia/patient-memory-js` on purpose — an upgrading consumer needs to know what the package used to be called.
|
|
28
|
+
|
|
3
29
|
## 0.5.0-rc.2
|
|
4
30
|
|
|
5
31
|
## 0.5.0-rc.1
|