Skip to content

[SDK] Feature: Allow forcing deploy/skip_deploy behaviour #19469

[SDK] Feature: Allow forcing deploy/skip_deploy behaviour

[SDK] Feature: Allow forcing deploy/skip_deploy behaviour #19469

Triggered via pull request February 27, 2025 22:58
Status Cancelled
Total duration 4m 36s
Artifacts

CI.yml

on: pull_request
optimize_ci
2s
optimize_ci
Matrix: E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Unit Tests
***#test: command (/home/runner/work/js/js/packages/***) /home/runner/setup-pnpm/node_modules/.bin/pnpm run test exited (1)
Unit Tests
Process completed with exit code 1.
Size
Canceling since a higher priority waiting request for 'CI-refs/pull/6361/merge' exists
Size
The operation was canceled.
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-card.tsx#L77
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-card.tsx#L86
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-row.tsx#L79
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-row.tsx#L113
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element