@ai-ecoverse/slicc-jsh 0.2.0 → 0.2.1

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 (7) hide show
  1. package/README.md +8 -3
  2. package/dist/host/jsh.mjs +9 -884
  3. package/dist/host/main.mjs +893 -0
  4. package/dist/jsh.mjs +252 -194
  5. package/dist/meta-main.json +1 -1
  6. package/dist/node.mjs +1014 -109
  7. package/package.json +17 -5
package/README.md CHANGED
@@ -35,7 +35,7 @@ JS program entries are **esbuild-bundled** to single files (`dist/node.mjs`, `di
35
35
 
36
36
  ## `jsh` outside SLICC
37
37
 
38
- The package's `bin` is the host `jsh` (`dist/host/jsh.mjs`), which runs `.jsh` scripts on the host's own Node 22+:
38
+ The package's `bin` is the host `jsh` (`dist/host/jsh.mjs`), which runs `.jsh` scripts on the host's own Node 22+. Inside slicc-kernel (a global `pnpm add -g` puts this `bin` on `PATH` ahead of the kernel's `jsh`), it hands off to the kernel jsh instead:
39
39
 
40
40
  ```bash
41
41
  npm i -g @ai-ecoverse/slicc-jsh
@@ -63,6 +63,11 @@ npm run golden:record
63
63
  npm run jsh:record # .jsh cases under test/jsh/fixtures/, recorded with the host jsh
64
64
  ```
65
65
 
66
- ## Publish
66
+ ## Release
67
67
 
68
- Publish goes through `.github/workflows/publish.yml` (`workflow_dispatch` with `run` + `certified` sha). Stable versions (no `-` in the version) publish to `latest` and also advance the `next` dist-tag; prereleases publish to `next` only. Certification and publish are coordinator-owned; agents do not publish.
68
+ Releases are cut by [semantic-release](https://semantic-release.gitbook.io/) on every push to `main` (`.github/workflows/release.yml`, the shared `node-release.yml` from slicc-shared-web), as in the sibling repos. It runs `npm run lint` and `npm test` (golden, `.jsh` parity, kernel integration), then derives the version from the commits since the last `v*` tag:
69
+ - a `feat:` commit gives a minor release (0.x stays 0.x until a breaking change);
70
+ - a `fix:` or `perf:` commit gives a patch release;
71
+ - other types (`chore:`, `docs:`, `ci:`, `test:`, `merge:`, …) release nothing.
72
+
73
+ It publishes to npm `latest` with trusted publishing (OIDC) and provenance, and creates a GitHub release. `version` in `package.json` stays `0.0.0`; semantic-release sets the real one when it publishes. npm has to trust `release.yml` for this package once: `npm run trust` (fledgling) sets that up, and `npm run trust:dry` shows what it would do.