@temir.ra/create-ts-lib 0.2.2 → 0.2.3

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Version 0
 
+## 0.2.3
+
+1. Updated change management workflow in `README.md` and `template/README.md`: build step now happens after merge (not before PR), so `buildinfo.txt` captures the correct git hash and artifacts are up to date before publish.
+2. Added Change Management section to root and template `CLAUDE.md`.
+
 ## 0.2.2
 
 1. Fixed `CHANGELOG.md` and `buildinfo.txt` copy paths in `cli.ts`: they were resolved relative to `template/` instead of the package root, causing the copy to fail. Refactored URL/path construction to derive all paths from a single `packageUrl`, eliminating redundant `fileURLToPath` calls at each copy site.

package/README.md

@@ -453,8 +453,9 @@ bun run dist/cli.bundle.js -- example
 2. Make the changes and commit.
 3. Bump the version in [`package.json`](package.json).
 4. Add an entry for the new version in [`CHANGELOG.md`](CHANGELOG.md).
-5. Run `bun run build`.
-6. Pull request the branch and publish.
+5. Pull request the branch.
+6. After merge, run `bun run build`.
+7. Publish
 
 ## Publish
 

package/buildinfo.txt

@@ -1 +1 @@
-0.2.2+77ce44b
+0.2.3+0a2de3a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@temir.ra/create-ts-lib",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Typescript library template",
   "author": "temir.ra",
   "license": "MIT",

package/template/CLAUDE.md

@@ -153,6 +153,16 @@ Key `package.json` fields:
 - `"sideEffects": false` — enables full tree-shaking by bundlers
 - `"imports": { "#src/*.js": "./src/*.ts" }` — package-internal alias for `src/`; use as `import { foo } from "#src/module.js"`. **Only for `dev.ts`, `tests/`, and `scripts/`** — not for library source files compiled by `tsconfig.build.json`, as tsc emits the specifier verbatim and it would break in published unbundled output.
 
+## Change Management
+
+1. Branch off main.
+2. Make the changes and commit.
+3. Bump the version in [`package.json`](package.json).
+4. Add an entry for the new version in [`CHANGELOG.md`](CHANGELOG.md).
+5. Pull request the branch.
+6. After merge, run `bun run build`. ← must happen after merge so `buildinfo.txt` captures the correct git hash, and before publish so the artifacts are up to date.
+7. Publish.
+
 ## Publishing
 
 See [README.md](README.md) for registry setup and publish commands.

package/template/README.md

@@ -48,8 +48,9 @@ bun run dev
 2. Make the changes and commit.
 3. Bump the version in [`package.json`](package.json).
 4. Add an entry for the new version in [`CHANGELOG.md`](CHANGELOG.md).
-5. Run `bun run build`.
-6. Pull request the branch and publish.
+5. Pull request the branch.
+6. After merge, run `bun run build`.
+7. Publish
 
 ## Publish