Skip to content

chore: bump version to 0.2.14 and update CHANGELOG #43

chore: bump version to 0.2.14 and update CHANGELOG

chore: bump version to 0.2.14 and update CHANGELOG #43

Triggered via push March 16, 2026 11:24
Status Success
Total duration 1m 12s
Artifacts

test.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
test (18.x)
Process completed with exit code 1.
test/version.test.ts > commit-msg CLI version tests > should output version in development mode with correct prefix: test/version.test.ts#L26
Error: Command failed: npm run dev:node20 -- --version npm warn exec The following package was not found and will be installed: tsx@4.21.0 npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open '/home/runner/.npm/_npx/fd45a72a545557e9/node_modules/@esbuild/linux-x64/package.json' npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open '/home/runner/.npm/_npx/fd45a72a545557e9/node_modules/@esbuild/linux-x64/README.md' npm error code ENOENT npm error syscall spawn sh npm error path /home/runner/.npm/_npx/fd45a72a545557e9/node_modules/esbuild npm error errno -2 npm error enoent spawn sh ENOENT npm error enoent This is related to npm not being able to find a file. npm error enoent npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-16T11_24_53_602Z-debug-0.log ❯ test/version.test.ts:26:22 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { status: 254, signal: null, output: [ null, '\n> @ai-coding-workshop/commit-msg@0.2.14 dev:node20\n> NODE_ENV=development NODE_OPTIONS=--no-warnings npx tsx src/bin/commit-msg.dev.ts --version\n\n', 'npm warn exec The following package was not found and will be installed: tsx@4.21.0\nnpm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open \'/home/runner/.npm/_npx/fd45a72a545557e9/node_modules/@esbuild/linux-x64/package.json\'\nnpm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open \'/home/runner/.npm/_npx/fd45a72a545557e9/node_modules/@esbuild/linux-x64/README.md\'\nnpm error code ENOENT\nnpm error syscall spawn sh\nnpm error path /home/runner/.npm/_npx/fd45a72a545557e9/node_modules/esbuild\nnpm error errno -2\nnpm error enoent spawn sh ENOENT\nnpm error enoent This is related to npm not being able to find a file.\nnpm error enoent\nnpm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-16T11_24_53_602Z-debug-0.log\n' ], pid: 3645, stdout: '\n> @ai-coding-workshop/commit-msg@0.2.14 dev:node20\n> NODE_ENV=development NODE_OPTIONS=--no-warnings npx tsx src/bin/commit-msg.dev.ts --version\n\n', stderr: 'npm warn exec The following package was not found and will be installed: tsx@4.21.0\nnpm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open \'/home/runner/.npm/_npx/fd45a72a545557e9/node_modules/@esbuild/linux-x64/package.json\'\nnpm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open \'/home/runner/.npm/_npx/fd45a72a545557e9/node_modules/@esbuild/linux-x64/README.md\'\nnpm error code ENOENT\nnpm error syscall spawn sh\nnpm error path /home/runner/.npm/_npx/fd45a72a545557e9/node_modules/esbuild\nnpm error errno -2\nnpm error enoent spawn sh ENOENT\nnpm error enoent This is related to npm not being able to find a file.\nnpm error enoent\nnpm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-16T11_24_53_602Z-debug-0.log\n' }
test (18.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/