@awebai/oats 0.70.2 → 0.70.3
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/docs/release-notes/v0.70.3.md +28 -0
- package/docs/upgrading.md +5 -5
- package/package.json +1 -1
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
# OATS 0.70.3
|
|
2
|
+
|
|
3
|
+
Unreleased
|
|
4
|
+
|
|
5
|
+
A hotfix for the pi bridge's needs-input claim, which shipped in 0.70.2.
|
|
6
|
+
|
|
7
|
+
## Upgrade
|
|
8
|
+
|
|
9
|
+
- **The Desktop and the CLI** can be upgraded in either order.
|
|
10
|
+
- **The pi bridge** (`@awebai/oats-pi` 0.70.3) reaches each pi folder with
|
|
11
|
+
`oats update`.
|
|
12
|
+
|
|
13
|
+
## Fixed
|
|
14
|
+
|
|
15
|
+
- **pi bridge: a question left by a pi that died while another pi's clear was
|
|
16
|
+
under way no longer stands unseen**
|
|
17
|
+
([oats-project/oats#2076](https://github.com/oats-project/oats/issues/2076)).
|
|
18
|
+
When a second pi in a home (a nested one, a subagent's session) opened a
|
|
19
|
+
dialog and died in the moment the live pi's bridge was clearing its own
|
|
20
|
+
claim, that bridge removed the dead pi's mark and left its `question` claim.
|
|
21
|
+
With no mark, the live pi did not clear it until it next showed a claim of
|
|
22
|
+
its own: in a quiet session the instance showed as needing input and its
|
|
23
|
+
scheduled wakes were held until the home's next pi ran, or
|
|
24
|
+
`oats instance waiting clear --producer oats.pi --home <home>`. The bridge
|
|
25
|
+
now removes only the mark its clear answered, and clears such a question in
|
|
26
|
+
the same step ([Whose claim it is](../capabilities.md#oatscore-needs-input)).
|
|
27
|
+
It reaches each pi folder with the bridge's next update
|
|
28
|
+
([upgrading](../upgrading.md)).
|
package/docs/upgrading.md
CHANGED
|
@@ -6,12 +6,12 @@ host that comes from it.
|
|
|
6
6
|
|
|
7
7
|
## Upgrading to the latest version
|
|
8
8
|
|
|
9
|
-
The latest version is **OATS 0.70.
|
|
10
|
-
The 0.70.
|
|
9
|
+
The latest version is **OATS 0.70.3** ([release notes](release-notes/v0.70.3.md)).
|
|
10
|
+
The 0.70.3 Desktop accepts OATS CLIs `>=0.26.0`, tested through 0.70: the
|
|
11
11
|
Desktop and the CLI can be upgraded [in either order](#either-order-works).
|
|
12
12
|
|
|
13
13
|
**First, read the `## Upgrade` section of every release after yours, up to
|
|
14
|
-
0.70.
|
|
14
|
+
0.70.3,** in the [release notes](release-notes/): it says what to do before
|
|
15
15
|
the CLI changes, and what else must change with it (the Desktop, another
|
|
16
16
|
tool, a package pin). [Coming from an older version](#coming-from-an-older-version)
|
|
17
17
|
names the releases that ask for more than the steps below. `oats version`
|
|
@@ -20,8 +20,8 @@ prints the version you have.
|
|
|
20
20
|
Then, on each host:
|
|
21
21
|
|
|
22
22
|
```sh
|
|
23
|
-
# 0. where the Desktop is installed: Desktop 0.70.
|
|
24
|
-
npm install -g @awebai/oats@0.70.
|
|
23
|
+
# 0. where the Desktop is installed: Desktop 0.70.3, in either order
|
|
24
|
+
npm install -g @awebai/oats@0.70.3 # 1. the CLI
|
|
25
25
|
oats update # 2. in each deployment: the plan, then it asks before it runs
|
|
26
26
|
oats doctor # 3. in the same deployment
|
|
27
27
|
```
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@awebai/oats",
|
|
3
|
-
"version": "0.70.
|
|
3
|
+
"version": "0.70.3",
|
|
4
4
|
"description": "OATS (Open Agent Team Specification) — durable souls, disposable instances, targetable capability packages, and the runtime-neutral oats CLI/kernel.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"agents",
|