Skip to content
Release

Fix CI: run send.test.ts in separate process to avoid mock.module pol… #10

Sign in to view logs

Fix CI: run send.test.ts in separate process to avoid mock.module pol…

Fix CI: run send.test.ts in separate process to avoid mock.module pol… #10

Triggered via push March 18, 2026 14:56
@guo-yuguo-yu
pushed 9160ec9
v1.1.0
Status Failure
Total duration 34s
Artifacts 4

release.yml

on: push
Matrix: build
publish
18s
publish
release
11s
release
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 6 warnings
publish
Process completed with exit code 1.
error: expect(received).toThrow(expected): test/unit/send.test.ts#L103
Expected substring: "Unknown send provider: unknown" Received message: "resend_api_key not configured. Run: mails config set resend_api_key <key>" at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:103:15)
error: resend_api_key not configured. Run: mails config set resend_api_key <key>: src/core/send.ts#L12
at resolveProvider (/home/runner/work/mails/mails/src/core/send.ts:12:19) at send (/home/runner/work/mails/mails/src/core/send.ts:23:20) at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:91:11)
error: expect(received).toThrow(expected): test/unit/send.test.ts#L80
Expected substring: "Either text or html body is required" Received message: "resend_api_key not configured. Run: mails config set resend_api_key <key>" at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:80:15)
error: expect(received).toThrow(expected): test/unit/send.test.ts#L74
Expected substring: "No \"from\" address" Received message: "resend_api_key not configured. Run: mails config set resend_api_key <key>" at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:74:15)
error: resend_api_key not configured. Run: mails config set resend_api_key <key>: src/core/send.ts#L12
at resolveProvider (/home/runner/work/mails/mails/src/core/send.ts:12:19) at send (/home/runner/work/mails/mails/src/core/send.ts:23:20) at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:51:11)
error: resend_api_key not configured. Run: mails config set resend_api_key <key>: src/core/send.ts#L12
at resolveProvider (/home/runner/work/mails/mails/src/core/send.ts:12:19) at send (/home/runner/work/mails/mails/src/core/send.ts:23:20) at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:33:26)
build (ubuntu-latest, bun-linux-x64, mails-linux-x64)
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/upload-artifact@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/
build (macos-latest, bun-darwin-arm64, mails-darwin-arm64)
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/upload-artifact@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/
build (ubuntu-24.04-arm, bun-linux-arm64, mails-linux-arm64)
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/upload-artifact@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/
build (macos-latest, bun-darwin-x64, mails-darwin-x64)
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/upload-artifact@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/
publish
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/
release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, softprops/action-gh-release@v2. 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/

Artifacts

Produced during runtime
Name Size Digest
mails-darwin-arm64 Expired
22 MB
sha256:d9d0eabeb117602e6a1398bed5c7aa798012517ab70681e8d95a0308a108bc22
mails-darwin-x64 Expired
23.8 MB
sha256:b27747f4d39b277e2c5e44380ec1004eafd7704f847cc9056910423f7538faff
mails-linux-arm64 Expired
37.5 MB
sha256:3f8cb47eeda0e503d038fc7cafd490e210345244003ddd30415c7b2ddcfcd6d0
mails-linux-x64 Expired
37.4 MB
sha256:a6b3c695a6ecd7bfeddc44632392394e8faa1a95bba664ea4ee578031c25f1a9