Create v0.1.5 release PR metadata updates

CHANGELIST.md

@@ -2,10 +2,16 @@
 
 ## Changelog
 
+# v0.1.5 May 13th, 2026
+
+## Changelog
+
 - [Breaking][Tooling] Updated the CI Node.js matrix to `18`, `20`, `22`, and `24`; removed Node.js `16`.
   - Why: Node.js 16 is EOL and current dependencies (for example `@pnpm/error` and `puppeteer`) now require Node.js 18+.
   - Why: CI started failing on Node.js 16 because required runtime features like `structuredClone` are not available.
 
+[Full changelog](https://github.com/nevware21/ts-build-tools/compare/0.1.4...0.1.5)
+
 # v0.1.4 Nov 18th, 2024
 
 ## Changelog

lib/coverage-tools/README.md

@@ -17,7 +17,7 @@ Install the npm packare: `npm install @nevware21/coverage-tools --save-dev`
 > It is suggested / recommended that you use the following definition in your `package.json` so that you are compatible with any future releases as they become available
 > we do not intend to make ANY known breaking changes moving forward until v2.x 
 > ```json
-> "@nevware21/coverage-tools": ">= 0.1.4 < 2.x"
+> "@nevware21/coverage-tools": ">= 0.1.5 < 2.x"
 > ```
 
 And then just used the helper in your package.json

lib/coverage-tools/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@nevware21/coverage-tools",
     "description": "Tools for merging coverage reports.",
-    "version": "0.1.4",
+    "version": "0.1.5",
     "homepage": "https://github.com/nevware21/ts-build-tools",
     "license": "MIT",
     "author": {
@@ -66,7 +66,7 @@
         "@rollup/plugin-json": "^6.0.0",
         "@rollup/plugin-node-resolve": "^16.0.0",
         "@rollup/plugin-strip": "^3.0.2",
-        "@nevware21/publish-npm": "0.1.4",
+        "@nevware21/publish-npm": "0.1.5",
         "@types/istanbul-lib-coverage": "^2.0.0",
         "@types/istanbul-lib-report": "^3.0.0",
         "@types/istanbul-reports": "^3.0.2",

lib/pre-proc/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@nevware21/ts-preproc",
     "description": "TypeScript pre-processing tools.",
-    "version": "0.1.4",
+    "version": "0.1.5",
     "homepage": "https://github.com/nevware21/ts-build-tools",
     "license": "MIT",
     "author": {
@@ -80,8 +80,8 @@
     "devDependencies": {
         "@microsoft/api-extractor": "^7.34.4",
         "@nevware21/tripwire": ">= 0.1.8 < 2.x",
-        "@nevware21/coverage-tools": "0.1.4",
-        "@nevware21/publish-npm": "0.1.4",
+        "@nevware21/coverage-tools": "0.1.5",
+        "@nevware21/publish-npm": "0.1.5",
         "@rollup/plugin-commonjs": "^29.0.0",
         "@rollup/plugin-json": "^6.0.0",
         "@rollup/plugin-node-resolve": "^16.0.0",

lib/publish-npm/README.md

@@ -18,7 +18,7 @@ Install the npm packare: `npm install @nevware21/publish-npm --save-dev`
 > It is suggested / recommended that you use the following definition in your `package.json` so that you are compatible with any future releases as they become available
 > we do not intend to make ANY known breaking changes moving forward until v2.x 
 > ```json
-> "@nevware21/publish-npm": ">= 0.1.4 < 2.x"
+> "@nevware21/publish-npm": ">= 0.1.5 < 2.x"
 > ```
 
 Create a configuration file with your group settings, where the

lib/publish-npm/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@nevware21/publish-npm",
     "description": "Tools to automate the publishing packages to npm.",
-    "version": "0.1.4",
+    "version": "0.1.5",
     "homepage": "https://github.com/nevware21/ts-build-tools",
     "license": "MIT",
     "author": {

package.json

@@ -1,7 +1,7 @@
 {
     "name": "@nevware21/ts-build-tools",
     "description": "A mono-repo for @nevware21 build-tools.",
-    "version": "0.1.4",
+    "version": "0.1.5",
     "homepage": "https://github.com/nevware21/ts-build-tools",
     "sideEffects": false,
     "license": "MIT",