Skip to content

feat: add ttl support at task and config levels #5005

feat: add ttl support at task and config levels

feat: add ttl support at task and config levels #5005

Re-run triggered March 11, 2026 16:56
Status Success
Total duration 1m 59s
Artifacts 17

pr_checks.yml

on: pull_request
Matrix: units / internal / 🧪 Unit Tests: Internal
Matrix: units / packages / 🧪 Unit Tests: Packages
Matrix: units / webapp / 🧪 Unit Tests: Webapp
typecheck  /  typecheck
8m 0s
typecheck / typecheck
sdk-compat  /  Bun Runtime
2m 29s
sdk-compat / Bun Runtime
sdk-compat  /  Deno Runtime
1m 57s
sdk-compat / Deno Runtime
sdk-compat  /  Cloudflare Workers
2m 3s
sdk-compat / Cloudflare Workers
Matrix: e2e / cli-v3
Matrix: sdk-compat / node-compat
units  /  ...  /  📊 Merge Reports
3m 42s
units / internal / 📊 Merge Reports
units  /  ...  /  📊 Merge Reports
19s
units / packages / 📊 Merge Reports
units  /  ...  /  📊 Merge Reports
39s
units / webapp / 📊 Merge Reports
Fit to window
Zoom out
Zoom in

Annotations

1 warning
e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, buildjet/setup-node@v4, pnpm/action-setup@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/