Skip to content

feat(site): add chat spend limit UI #62042

feat(site): add chat spend limit UI

feat(site): add chat spend limit UI #62042

Triggered via pull request March 17, 2026 00:30
Status Success
Total duration 8m 8s
Artifacts 1

ci.yaml

on: pull_request
Matrix: test-e2e
Matrix: test-go-pg
test-go-tailnet-integration
0s
test-go-tailnet-integration
chromatic
3m 0s
chromatic
deploy  /  should-deploy
deploy / should-deploy
deploy  /  deploy
deploy / deploy
notify-slack-on-failure
0s
notify-slack-on-failure
deploy  /  deploy-wsproxies
deploy / deploy-wsproxies
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 8 warnings
gen
found 6 metrics
gen
found 13 metrics
gen
found 2 metrics
gen
found 2 metrics
gen
found 2 metrics
gen
found 1 metrics
gen
found 1 metrics
gen
found 7 metrics
gen
found 2 metrics
gen
found 3 metrics
changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
chromatic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@0a44ba7841725637a19e28fa30b79a866c81b0a6, chromaui/action@07791f8243f4cb2698bf4d00426baf4b2d1cb7e0, pnpm/action-setup@fe02b34f77f8bc703788d5817da081398fad5dd2, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
chromatic
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0eKG4aQAAAAAUSOHJK/YcQ7pi3sbvMe+2UEFPRURHRTA1MTQARWRnZQ==
chromatic
Failed to restore: Cache service responded with 400
test-e2e
Failed to save: commitCache failed: Cache service responded with 500
test-e2e
No files were found with the provided path: ./site/test-results/**/debug-pprof-*.txt. No artifacts will be uploaded.
test-e2e
No files were found with the provided path: ./site/test-results/**/*.webm. No artifacts will be uploaded.
required
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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
coderd-debug-logs Expired
118 KB
sha256:fdb1494f0883e58e0f2bfab2ff4bdfa2f9d0cbf8f46c39b949285ee463e7608c