@marcopeg/hal 1.0.27 → 1.0.28

package/README.md

@@ -177,13 +177,18 @@ The engine can send files back through Telegram. Each user has a `downloads/` fo
 
 ## Releasing
 
-Releases use [conventional commits](https://www.conventionalcommits.org/) to drive `CHANGELOG.md` generation.
+Releases use [release-it](https://github.com/release-it/release-it) with [conventional commits](https://www.conventionalcommits.org/) for versioning and changelog, then you publish with npm so the browser/OTP flow works normally.
 
-1. **Clean tree** — Commit or stash all changes so the working tree is clean.
-2. **Auth** — Run `npm login` if you are not already logged in to the registry.
-3. **Release** — Run `pnpm run deploy` (or `npm run deploy`). This runs `npm version patch` then `npm publish --access public`. The `version` script regenerates `CHANGELOG.md` from commits since the last tag and adds it to the release commit before the version tag is created.
+**Package manager:** This repo uses **pnpm** (see `packageManager` in `package.json`). You can use **npm** instead; Node 18+ and `npm login` are the only requirements.
 
-For a minor or major bump, run `npm version minor` or `npm version major` (which also runs the changelog step), then `npm publish --access public`.
+1. **Clean tree** — Commit or stash all changes. release-it will refuse to run if the working directory is dirty.
+2. **Auth** — Run `npm login` if you are not already logged in.
+3. **Version + changelog** — Either:
+   - **Patch:** `pnpm run deploy` or `npm run deploy` — non-interactive patch bump, updates `CHANGELOG.md`, commit, and tag.
+   - **Interactive (patch/minor/major):** `pnpm run release` or `npm run release` — choose the bump, then same (changelog, commit, tag).
+4. **Publish** — Run `pnpm run publish` or `npm run publish`. This runs `npm publish --access public` in your terminal, so npm can open the browser or prompt for your OTP as usual when you have 2FA enabled.
+
+Config: [.release-it.json](.release-it.json) (conventional-commits preset, `CHANGELOG.md` at repo root). release-it is configured not to run publish; the separate publish step keeps the flow simple and restores the normal npm 2FA experience.
 
 ## Security Notice
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@marcopeg/hal",
-  "version": "1.0.27",
+  "version": "1.0.28",
   "type": "module",
   "main": "dist/index.js",
   "bin": {
@@ -17,10 +17,12 @@
     "typecheck": "tsc --noEmit",
     "lint": "biome check src",
     "lint:fix": "biome check --write src",
-    "prepublishOnly": "pnpm run build",
+    "prepublishOnly": "npm run build",
     "sync-skills": "node .agents/scripts/sync-skills.mjs",
     "prepare": "husky",
-    "deploy": "npm version patch && npm publish --access public",
+    "release": "release-it",
+    "deploy": "release-it patch --ci",
+    "publish": "npm publish --access public",
     "docs": "npx mdts"
   },
   "keywords": [
@@ -40,7 +42,7 @@
   "description": "Telegram bot for AI coding agents. Multi-project and multi-engine: run Claude Code, Copilot, Codex, or OpenCode per project, each with its own bot.",
   "repository": {
     "type": "git",
-    "url": "https://github.com/marcopeg/hal.git"
+    "url": "git+https://github.com/marcopeg/hal.git"
   },
   "dependencies": {
     "chokidar": "^5.0.0",
@@ -54,8 +56,10 @@
   },
   "devDependencies": {
     "@biomejs/biome": "^2.3.11",
+    "@release-it/conventional-changelog": "^10.0.0",
     "@types/node": "^25.0.8",
     "husky": "^9.1.7",
+    "release-it": "^19.0.0",
     "tsx": "^4.21.0",
     "typescript": "^5.9.3"
   },