genesis-compiler 1.9.1 → 1.9.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 CHANGED
@@ -1120,39 +1120,21 @@ Initialization creates an empty map without replacing one.
1120
1120
 
1121
1121
  ## Publishing this repository
1122
1122
 
1123
- The release command uses `NPM_TOKEN` in the command's environment on a local
1124
- computer, CI runner, or hosted development environment. Supply a token with
1125
- publishing access to the selected package. In Vibe64, save it in the project's
1126
- **Env → Development**, enable **Secret**, and choose **Add**. Managed shell
1127
- commands receive the saved value; credentials do not belong in source or chat.
1128
-
1129
- Update the selected package's version and lockfile (for the compiler, also the
1130
- packaged Codex plugin version in `plugins/genesis/.codex-plugin/plugin.json`,
1131
- which must equal `package.json`), run the relevant checks,
1132
- then commit and push the release source to `main`. Publish from a clean checkout
1133
- whose `HEAD` matches `origin`'s actual `main`, with development dependencies
1134
- installed through `npm ci`:
1135
-
1136
- ```bash
1137
- npm run release:npm:publish -- compiler --dry-run
1138
- # When the catalog also changed, publish it before the compiler:
1139
- npm run release:npm:publish -- stack
1140
- npm run release:npm:publish -- compiler
1141
- ```
1142
-
1143
- Select `compiler` for `genesis-compiler` or `stack` for `genesis-stack`.
1144
- Dry runs pack the selected source and check the registry without uploading,
1145
- requiring a token, or requiring a clean published checkout. Real publishing
1146
- checks npm authentication and the exact version before uploading. Matching
1147
- releases are skipped; different contents under an existing version fail with
1148
- the first differing file. Registry errors stop the operation. Tarball hashes
1149
- are compared first; a different hash triggers a comparison of verified archive
1150
- files and permissions, ignoring container timestamps and compression.
1151
- The checked candidate tarball is the uploaded tarball. Temporary tarballs and
1152
- private npm configuration are removed on success or failure. The command does
1153
- not change versions or run tests. Published versions are immutable; after an
1154
- interrupted upload, rerun the same committed release to skip matching versions.
1155
-
1156
- Hosted working sessions normally use a session branch. After saving or merging
1157
- the work to `main`, publish from a separate clean clone of that published branch
1158
- using the project's managed shell. Keep the working session on its own branch.
1123
+ Genesis has no release command of its own. `genesis-compiler` and
1124
+ `genesis-stack` are released by the Vibe64 Online deploy, which runs the
1125
+ published JSKIT release tool against a clean clone of this repository's `main`.
1126
+ Genesis does not depend on that tool.
1127
+
1128
+ The release covers both packages: the root `genesis-compiler` and
1129
+ `packages/genesis-stack`, which the root reaches through its `file:`
1130
+ development dependency. A package whose packed contents differ from its current
1131
+ npm version receives a patch version increment; unchanged packages keep their
1132
+ version and are not republished. The catalog is published before the compiler.
1133
+ The root `package.json` `jskitRelease.versionFiles` entry keeps the packaged
1134
+ Codex plugin version in `plugins/genesis/.codex-plugin/plugin.json` equal to
1135
+ the compiler version, because Codex compares an installed plugin with that
1136
+ manifest. The release commits the version changes to `main` as
1137
+ `Release <package@version, ...>` and pushes them.
1138
+
1139
+ Changes reach npm only through that deploy. Commit and push them to `main` as
1140
+ usual; there is nothing to version or publish by hand.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "genesis-compiler",
3
- "version": "1.9.1",
3
+ "version": "1.9.2",
4
4
  "type": "module",
5
5
  "description": "An agent-independent prompt, multi-language code-index, cleanup, and verification companion with project agent guidance.",
6
6
  "repository": {
@@ -47,9 +47,13 @@
47
47
  "docs/parsers.md"
48
48
  ],
49
49
  "scripts": {
50
- "release:npm:publish": "node scripts/release-npm.mjs",
51
50
  "test": "node --test --test-concurrency=1 test/*.test.js"
52
51
  },
52
+ "jskitRelease": {
53
+ "versionFiles": [
54
+ "plugins/genesis/.codex-plugin/plugin.json"
55
+ ]
56
+ },
53
57
  "dependencies": {
54
58
  "@ast-grep/napi": "^0.45.1",
55
59
  "mdast-util-from-markdown": "^2.0.3",
@@ -58,7 +62,6 @@
58
62
  },
59
63
  "devDependencies": {
60
64
  "@ast-grep/lang-python": "0.0.6",
61
- "genesis-stack": "file:packages/genesis-stack",
62
- "tar": "7.5.22"
65
+ "genesis-stack": "file:packages/genesis-stack"
63
66
  }
64
67
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "genesis",
3
- "version": "1.9.1",
3
+ "version": "1.9.2",
4
4
  "description": "Makes Codex aware of optional Genesis adoption for existing projects.",
5
5
  "author": {
6
6
  "name": "Mobily Enterprises"