@golba98/codexa 1.0.7 → 1.0.8

package/README.md

@@ -469,6 +469,7 @@ UI-only preferences are stored in `~/.codexa-settings.json` (separate from runti
 
 - [Architecture](docs/ARCHITECTURE.md) explains Codexa's entry points, subsystem boundaries, prompt and rendering flows, provider layers, state model, persistence, and maintenance invariants with diagrams.
 - [Source Guide](docs/SOURCE_GUIDE.md) catalogs the purpose of every file under `src/` and records the maintenance rules for each source area.
+- [Release Guide](docs/RELEASING.md) documents the validation, version bump, and NPM publishing commands.
 - [Developer Scripts](scripts/README.md) lists every package command and explains launcher, shim, audit, build-metadata, smoke, and test behavior.
 
 ## Local Development
@@ -532,63 +533,6 @@ This replaces the global `codexa` with a symlink to the repo. Undo with `npm unl
 npm install -g .
 ```
 
-## Maintainer release and NPM publishing
-
-The package name is `@golba98/codexa`. Publish from the repository root, and
-increment `version` in `package.json` before each release. NPM versions are
-immutable, so never reuse a version that has already been published.
-
-Check the current local and registry versions:
-
-```bash
-npm pkg get name version
-npm whoami
-npm view @golba98/codexa version
-npm view @golba98/codexa dist-tags --json
-```
-
-Run the release checks:
-
-```bash
-bun install
-bun run typecheck
-bun test
-git diff --check
-```
-
-Inspect exactly what will be included in the package:
-
-```bash
-npm pack --dry-run
-```
-
-Publish the next version publicly:
-
-```bash
-npm publish --access public
-```
-
-`npm publish` automatically runs `prepublishOnly`, which regenerates build
-metadata, typechecks, and runs the full test suite. Verify the registry and
-the installed command after publishing:
-
-```bash
-npm view @golba98/codexa version
-npm view @golba98/codexa dist-tags --json
-npm install -g @golba98/codexa@latest
-codexa --version
-```
-
-If the release is tracked in Git, commit the version and generated build-info
-change, then tag and push it:
-
-```bash
-git add package.json src/config/buildInfo.ts README.md scripts/README.md
-git commit -m "release: publish Codexa vX.Y.Z"
-git tag vX.Y.Z
-git push origin main --follow-tags
-```
-
 ## Testing
 
 ```bash
@@ -708,9 +652,9 @@ If you expect a notice but don't see one:
 
 See [CHANGELOG.md](CHANGELOG.md) for the full release history.
 
-**Current release: v1.0.7**
+**Current release: v1.0.8**
 
-v1.0.7 keeps workspaces clean: provider choices, imported attachments, and default diagnostic logs now live in Codexa user data instead of a project-local `.codexa` directory.
+v1.0.8 is a packaging-maintenance release that normalizes the published executable path without changing runtime behavior.
 
 Other recent releases introduce major additions, including:
 - **Mistral Vibe CLI Routing**: Connect through the `vibe` CLI tool (`vibe --setup`).

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@golba98/codexa",
-  "version": "1.0.7",
+  "version": "1.0.8",
   "description": "Terminal UI for Codexa — TypeScript + Bun + Ink",
   "type": "module",
   "bin": {
-    "codexa": "./bin/codexa.js"
+    "codexa": "bin/codexa.js"
   },
   "scripts": {
     "start": "bun run --silent src/index.tsx",

package/src/config/buildInfo.ts

@@ -1,3 +1,3 @@
 // Generated by scripts/gen-build-info.mjs — do not edit manually.
-export const BUILD_COMMIT = "c04f84f315a4b2c4b8bea27d41ac370a27467572" as const;
-export const APP_VERSION = "1.0.7" as const;
+export const BUILD_COMMIT = "931172a9e537e5e55979677187f4eeaeadcb654a" as const;
+export const APP_VERSION = "1.0.8" as const;