@sjawhar/pi-envoy 16.12.1 → 16.13.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.
package/README.md CHANGED
@@ -162,8 +162,8 @@ omp plugin install @sjawhar/pi-envoy
162
162
  ```
163
163
 
164
164
  A session that had the pre-split package installed (the one package that carried both entries
165
- until 7.x) uninstalls it and installs this one once; the `CHANGELOG.md` entry that renames the
166
- package `@sjawhar/pi-envoy` gives the two commands. A Legion deployment installs
165
+ until 7.x) uninstalls it and installs this one once; `CHANGELOG.md`, this package's history, gives
166
+ the two commands in the entry that renamed the package. A Legion deployment installs
167
167
  `@sjawhar/pi-legion` as well (`packages/pi-legion/README.md`); the daemon's boot gate refuses a
168
168
  pane that still loads the pre-split package beside the new ones.
169
169
 
@@ -189,8 +189,9 @@ for `omp.extensions` (only `omp.skills` ships as committed, since `dist/skills`
189
189
  a repo checkout after the prepack and the published tarball), while the committed manifest keeps
190
190
  the TypeScript entry for repo checkouts. In `.github/workflows/release.yaml`, the `pi_envoy_build`
191
191
  job rewrites the manifest before `bun pm pack` and uploads the tarball (its tree is discarded,
192
- nothing is restored); the `publish` job publishes that tarball and commits the version bump to the
193
- committed manifest, touching `.version` alone.
192
+ nothing is restored); the `publish` job publishes that tarball, and nothing commits a version: the
193
+ committed manifest's `.version` stays where it last was, and the `pi-envoy-v` tag the release makes
194
+ is what records the release, with this release's changelog entries in its GitHub release notes.
194
195
  Packing with the committed source manifest is refused by the prepack, because such a tarball would
195
196
  point OMP at an extension file it does not contain.
196
197
 
package/dist/envoy.js CHANGED
@@ -41189,7 +41189,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
41189
41189
 
41190
41190
  // package.json
41191
41191
  var name = "@sjawhar/pi-envoy";
41192
- var version2 = "16.12.1";
41192
+ var version2 = "16.13.0";
41193
41193
  var package_default = {
41194
41194
  name,
41195
41195
  version: version2,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-envoy",
3
- "version": "16.12.1",
3
+ "version": "16.13.0",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {