Fix CI: only run unit + mock E2E tests in release workflow #7
guo-yurelease.yml
on: push
Matrix: build
publish
19s
release
13s
Annotations
8 errors and 6 warnings
|
publish
Process completed with exit code 1.
|
|
error: expect(received).toThrow(expected):
test/unit/send.test.ts#L113
Expected substring: "Unknown send provider: unknown"
Received message: "Unknown send provider: undefined"
at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:113:15)
|
|
error: Unknown send provider: undefined:
src/core/send.ts#L17
at resolveProvider (/home/runner/work/mails/mails/src/core/send.ts:17:17)
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:102:11)
|
|
error: expect(received).toThrow(expected):
test/unit/send.test.ts#L88
Expected substring: "Either text or html body is required"
Received message: "Unknown send provider: undefined"
at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:88:15)
|
|
error: expect(received).toThrow(expected):
test/unit/send.test.ts#L79
Expected substring: "No \"from\" address"
Received message: "Unknown send provider: undefined"
at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:79:15)
|
|
error: expect(received).toThrow(expected):
test/unit/send.test.ts#L68
Expected substring: "resend_api_key not configured"
Received message: "Unknown send provider: undefined"
at <anonymous> (/home/runner/work/mails/mails/test/unit/send.test.ts:68:15)
|
|
error: Unknown send provider: undefined:
src/core/send.ts#L17
at resolveProvider (/home/runner/work/mails/mails/src/core/send.ts:17:17)
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: Unknown send provider: undefined:
src/core/send.ts#L17
at resolveProvider (/home/runner/work/mails/mails/src/core/send.ts:17:17)
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:30: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:e3d840feeca1c50ffca09d5d837d2d268eebc976869deb27f27d1afc73027415
|
|
|
mails-darwin-x64
Expired
|
23.8 MB |
sha256:5300b88947f7bb629cb6de15bf9f4ff915a1a881d47fcb1cc1fc01fb27f784d9
|
|
|
mails-linux-arm64
Expired
|
37.5 MB |
sha256:8fd3941b35d06a382d0e6468be1b75908e93f8ac7dc7d9c81a0c5c364c206849
|
|
|
mails-linux-x64
Expired
|
37.4 MB |
sha256:e67dc9ddb5861cdb29d47a8fc436176022a966725a76515a0fb4de9ec42f9f43
|
|