@sjawhar/pi-envoy 10.1.0 → 10.1.2
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/README.md +4 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -95,8 +95,10 @@ that says which skills each ships: it builds this package's one entry, writes th
|
|
|
95
95
|
stages this package's partition into `dist/skills`. The published manifest exposes `dist/envoy.js`
|
|
96
96
|
for `omp.extensions` (only `omp.skills` ships as committed, since `dist/skills` is its path in both
|
|
97
97
|
a repo checkout after the prepack and the published tarball), while the committed manifest keeps
|
|
98
|
-
the TypeScript entry for repo checkouts. `.github/workflows/release.yaml
|
|
99
|
-
|
|
98
|
+
the TypeScript entry for repo checkouts. In `.github/workflows/release.yaml`, the `pi_envoy_build`
|
|
99
|
+
job rewrites the manifest before `bun pm pack` and uploads the tarball (its tree is discarded,
|
|
100
|
+
nothing is restored); the `pi_envoy_publish` job publishes that tarball and commits the version bump
|
|
101
|
+
to the committed manifest, touching `.version` alone.
|
|
100
102
|
Packing with the committed source manifest is refused by the prepack, because such a tarball would
|
|
101
103
|
point OMP at an extension file it does not contain.
|
|
102
104
|
|