@mercury-fw/cli 0.44.1 → 0.45.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 +18 -0
- package/package.json +5 -5
- package/src/catalog.ts +1 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# @mercury-fw/cli
|
|
2
2
|
|
|
3
|
+
## 0.45.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 812c9c5: - A conversation reopened on the HTTP surface after Mercury freed its history comes back to the model: the summaries of its older part plus its newest messages from the archive, within a budget.
|
|
8
|
+
- What a resumed conversation brings back isn't captured to long-term memory again, only the new messages are.
|
|
9
|
+
- `SESSION_RESUME_MAX_CHARS` sets how much comes back (default 30000, `0` turns it off); `HTTP_SURFACE_RESUME_MAX_CHARS` sets it for the HTTP surface only.
|
|
10
|
+
- `InboundTurn.resume` lets a channel mark a conversation its client reopens.
|
|
11
|
+
- The episodic collection gets a `sessionKey` index.
|
|
12
|
+
- `mfw create` lists `HTTP_SURFACE_RESUME_MAX_CHARS` for the HTTP channel.
|
|
13
|
+
- Core's README explains how Mercury remembers a conversation.
|
|
14
|
+
|
|
15
|
+
### Patch Changes
|
|
16
|
+
|
|
17
|
+
- Updated dependencies [812c9c5]
|
|
18
|
+
- @mercury-fw/core@0.45.0
|
|
19
|
+
- @mercury-fw/utils@0.45.0
|
|
20
|
+
|
|
3
21
|
## 0.44.1
|
|
4
22
|
|
|
5
23
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mercury-fw/cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.45.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -41,17 +41,17 @@
|
|
|
41
41
|
"comment:shape": "The Mercury CLI (`mfw`). `mfw create <dir>` writes a new Mercury app from the template. The framework packages move in lockstep with it, so a new app gets them at the CLI's own version; plugins and channels at the registry's latest. The plugin and channel packages are devDependencies only for the catalog test. `main(argv)` is exported for create-mercury-agent.",
|
|
42
42
|
"dependencies": {
|
|
43
43
|
"@clack/prompts": "^1.8.1",
|
|
44
|
-
"@mercury-fw/core": "0.
|
|
45
|
-
"@mercury-fw/utils": "0.
|
|
44
|
+
"@mercury-fw/core": "0.45.0",
|
|
45
|
+
"@mercury-fw/utils": "0.45.0",
|
|
46
46
|
"commander": "^15.0.0"
|
|
47
47
|
},
|
|
48
48
|
"devDependencies": {
|
|
49
49
|
"@mercury-fw/auth-oidc": "0.1.0",
|
|
50
50
|
"@mercury-fw/auth-static": "0.2.0",
|
|
51
51
|
"@mercury-fw/channel-google-chat": "0.6.0",
|
|
52
|
-
"@mercury-fw/channel-http": "0.
|
|
52
|
+
"@mercury-fw/channel-http": "0.8.0",
|
|
53
53
|
"@mercury-fw/directory-static": "0.1.0",
|
|
54
|
-
"@mercury-fw/formatter": "0.
|
|
54
|
+
"@mercury-fw/formatter": "0.45.0",
|
|
55
55
|
"@mercury-fw/plugin-atlassian-admin": "0.3.1",
|
|
56
56
|
"@mercury-fw/plugin-bitbucket": "0.3.1",
|
|
57
57
|
"@mercury-fw/plugin-jira": "0.6.1",
|
package/src/catalog.ts
CHANGED
|
@@ -60,6 +60,7 @@ export const CATALOG: CatalogEntry[] = [
|
|
|
60
60
|
{ name: "HTTP_SURFACE_PORT", comment: "Port of the HTTP surface", value: "4100" },
|
|
61
61
|
{ name: "HTTP_SURFACE_CORS_ORIGIN", comment: "Origin allowed to call the HTTP surface from a browser, if any" },
|
|
62
62
|
{ name: "HTTP_SURFACE_PUBLIC_URL", comment: "Address people's browsers reach the HTTP surface at, for logging in to the services plugins act on as them" },
|
|
63
|
+
{ name: "HTTP_SURFACE_RESUME_MAX_CHARS", comment: "Characters of a reopened conversation that come back to the model (empty: the core's SESSION_RESUME_MAX_CHARS, 0: off)" },
|
|
63
64
|
],
|
|
64
65
|
},
|
|
65
66
|
{
|