@olivervea/pipelines 2.0.0-beta.19 → 2.0.0-beta.20

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 +4 -4
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -11,7 +11,7 @@ Design: [`docs/design/pipelines-v2.md`](https://github.com/OliverVea/Olve.Pipeli
11
11
  The manifest format is in [`manifest.schema.json`](manifest.schema.json), generated from [`src/describe/manifest-schema.ts`](src/describe/manifest-schema.ts).
12
12
 
13
13
  ```
14
- sdk/
14
+ src/sdk/
15
15
  src/index.ts authoring API (`@olivervea/pipelines`)
16
16
  src/core/ models, secrets, config, steps, implement()
17
17
  src/builder/ pipeline builder (types + runtime records), Ref<T>
@@ -47,8 +47,8 @@ bunx olve-build . --out .olve/out
47
47
  ```
48
48
 
49
49
  - The package ships TypeScript sources (Bun runs them directly; `harness.sdkHash` hashes them), so the
50
- same version gives the same `sdkHash` and handler hashes from npm or from `file:../sdk`.
51
- - Inside this repo, `.pipelines/` and `.pipelines-test/` use `"@olivervea/pipelines": "file:../sdk"`.
50
+ same version gives the same `sdkHash` and handler hashes from npm or from `file:../src/sdk`.
51
+ - Inside this repo, `.pipelines/` and `.pipelines-test/` use `"@olivervea/pipelines": "file:../src/sdk"`.
52
52
 
53
53
  ### Releases
54
54
 
@@ -441,7 +441,7 @@ bun install --frozen-lockfile
441
441
  bunx olve-build .pipelines --out /work/out --upload-url "$STEP_PUT_URL" --sentinels
442
442
  ```
443
443
 
444
- From npm, nothing else is needed. A local `file:`/`link:` dependency (`"@olivervea/pipelines": "file:../sdk"`, as Olve.Pipelines' own `.pipelines/` does) resolves to its **source directory**, not the copy in `node_modules`, so its own dependencies must be installed there too: the build Job runs `bun install --frozen-lockfile --production` in every local dependency of the binding's `package.json` that is inside the repo, before building.
444
+ From npm, nothing else is needed. A local `file:`/`link:` dependency (`"@olivervea/pipelines": "file:../src/sdk"`, as Olve.Pipelines' own `.pipelines/` does) resolves to its **source directory**, not the copy in `node_modules`, so its own dependencies must be installed there too: the build Job runs `bun install --frozen-lockfile --production` in every local dependency of the binding's `package.json` that is inside the repo, before building.
445
445
 
446
446
  The repo depends on the SDK as a normal package. It resolves through `exports` (`@olivervea/pipelines`, `@olivervea/pipelines/harness`, `@olivervea/pipelines/testing`), and the tests cover this with a `file:` install. `bun` must be on `PATH`, because the bins use `#!/usr/bin/env bun`. A consumer `tsconfig.json` has to include the dot-directory explicitly (`"include": [".pipelines/**/*.ts"]`), and should exclude `.pipelines/.olve`.
447
447
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@olivervea/pipelines",
3
- "version": "2.0.0-beta.19",
3
+ "version": "2.0.0-beta.20",
4
4
  "description": "Olve.Pipelines v2 SDK: typed pipeline authoring, the step harness, and the build tool.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -9,7 +9,7 @@
9
9
  "repository": {
10
10
  "type": "git",
11
11
  "url": "git+https://github.com/OliverVea/Olve.Pipelines.git",
12
- "directory": "sdk"
12
+ "directory": "src/sdk"
13
13
  },
14
14
  "bugs": {
15
15
  "url": "https://github.com/OliverVea/Olve.Pipelines/issues"