eve-hub 0.14.11 → 0.14.12

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,11 @@
1
1
  # eve-hub
2
2
 
3
+ ## 0.14.12
4
+
5
+ ### Patch Changes
6
+
7
+ - A wake-up's `enable`, `disable` and `invoke` run without approval, like `create`, `update` and `delete`. eve asks for approval on every schedule write it isn't told about, so `schedule__wake__disable` waited on an approval no one was asked for and the turn hung.
8
+
3
9
  ## 0.14.11
4
10
 
5
11
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eve-hub",
3
- "version": "0.14.11",
3
+ "version": "0.14.12",
4
4
  "license": "Apache-2.0",
5
5
  "description": "Bot-side code shared by every hub agent: registry tools, the roster hook, the eve channel, the host sandbox and browser, and model helpers.",
6
6
  "type": "module",
package/schedules/wake.js CHANGED
@@ -57,7 +57,8 @@ const definition = defineDynamicSchedules({
57
57
  scope: byPrincipal,
58
58
  tool: true,
59
59
  // A wake-up only reaches the arming bot's own thread, and an unattended turn cannot wait for approval.
60
- approval: { create: () => "not-applicable", update: () => "not-applicable", delete: () => "not-applicable" },
60
+ // eve asks for approval on every write op not named here, so each one is.
61
+ approval: { create: () => "not-applicable", update: () => "not-applicable", delete: () => "not-applicable", enable: () => "not-applicable", disable: () => "not-applicable", invoke: () => "not-applicable" },
61
62
  preparePayload(input, context) {
62
63
  return { note: input.note, sessionId: context.session.id, until: Date.parse(input.until) };
63
64
  },