@silvermoon-work/task-sdk 0.1.0-canary-261111-2 → 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.
Files changed (2) hide show
  1. package/README.md +11 -11
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -7,17 +7,18 @@ callback/context types. It uses
7
7
 
8
8
  Migrated under the original MIT license from
9
9
  [potential-guide at 6614f46](https://github.com/shazhou-ww/potential-guide/tree/6614f46bf0f4152c61bd2c73d6c4b21ab4cf366f/packages/task-sdk).
10
- The runtime and public API are preserved; package imports now use the
10
+ The initial migration preserved the runtime and public API; package imports use the
11
11
  `@silvermoon-work` workspace. The initial `0.1.0-canary-261109-1` was published through
12
12
  [Trusted Publishing](https://github.com/silvermoon-work/task-engine/actions/runs/42588331015)
13
13
  with an exact dependency on protocol `0.1.0-canary-261109-2`.
14
- Select an explicit SDK version or the `canary` dist-tag; `latest` is still the
15
- `0.0.0` placeholder.
16
-
17
- The current source candidate is `0.1.0-canary-261110-1`, paired with protocol
18
- `0.1.0-canary-261110-1`. Publish these separately in dependency order only after
14
+ The current release candidate is `0.1.0`, paired with protocol
15
+ `0.1.0`, targeting `latest`. Publish these separately in dependency order only after
19
16
  the exact candidate receives approval; the manifest is not npm availability evidence.
20
17
 
18
+ The published `0.1.0-canary-261111-2` introduced the breaking Space context
19
+ contract; see the [release notes](../../README.md#space-context-canary-2026-11-11).
20
+ 0.1.0 retains that contract. Rebuild older canary Bundles for the new host protocol.
21
+
21
22
  Versions from `0.1.0-canary-261109-2` additionally restore `TaskContext.invokeTask`,
22
23
  `ChildTaskInvocation` author types and host-ACK child results, previously
23
24
  provided only by the old SDK in integration fixtures. These changes are not
@@ -28,14 +29,13 @@ in the initial canary above; use version 2 or later for child Tasks.
28
29
  Use the migrated workspace
29
30
  [task-builder CLI init](../task-builder-cli/README.md#init-composition)
30
31
  to create a private project, then build its module and CAR. Standalone `car`
31
- accepts `dist/task.yaml`; CAR inspection is a library operation, not a Builder
32
+ accepts `dist/<derived-package-name>/task.yaml`; CAR inspection is a library operation, not a Builder
32
33
  `check` command in the redesigned interface.
33
- Builder core version 2 and CLI version 1 generated the old SDK template;
34
- use core version 3 and CLI version 3 for the migrated default. Existing projects can
35
- explicitly select the SDK version with child invocation support:
34
+ Use the matching `0.1.0` Builder and CLI for Space-aware
35
+ templates. Existing projects can select the SDK explicitly:
36
36
 
37
37
  ```text
38
- pnpm add @silvermoon-work/task-sdk@0.1.0-canary-261109-2
38
+ pnpm add @silvermoon-work/task-sdk@0.1.0
39
39
  ```
40
40
 
41
41
  For the current workspace CLI:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@silvermoon-work/task-sdk",
3
- "version": "0.1.0-canary-261111-2",
3
+ "version": "0.1.0",
4
4
  "description": "Generation-scoped Task Worker runtime and author callback types.",
5
5
  "type": "module",
6
6
  "sideEffects": false,
@@ -22,7 +22,7 @@
22
22
  },
23
23
  "dependencies": {
24
24
  "multiformats": "14.0.5",
25
- "@silvermoon-work/task-protocol": "0.1.0-canary-261111-2"
25
+ "@silvermoon-work/task-protocol": "0.1.0"
26
26
  },
27
27
  "publishConfig": {
28
28
  "access": "public"