update dependencies (#6106) #18456
jnsdlsCI.yml
on: push
optimize_ci
2s
Build Packages
1m 14s
Lint Packages
2m 1s
Unit Tests
1m 29s
Size
0s
Matrix: E2E Tests
Annotations
18 errors and 11 warnings
|
E2E Tests (bun, esbuild)
Process completed with exit code 1.
|
|
E2E Tests (pnpm, vite)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (pnpm, esbuild)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (pnpm, webpack)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (npm, vite)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (npm, webpack)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (npm, esbuild)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (npm, esbuild)
The operation was canceled.
|
|
E2E Tests (bun, vite)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (bun, vite)
The operation was canceled.
|
|
E2E Tests (bun, webpack)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (bun, webpack)
The operation was canceled.
|
|
E2E Tests (yarn, esbuild)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (yarn, esbuild)
The operation was canceled.
|
|
E2E Tests (yarn, webpack)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (yarn, webpack)
The operation was canceled.
|
|
E2E Tests (yarn, vite)
The job was canceled because "bun_esbuild" failed.
|
|
E2E Tests (yarn, vite)
The operation was canceled.
|
|
optimize_ci
Request body: {"token":"***","caller":{"name":"graphite-ci-action","version":"0.0.0"},"context":{"kind":"GITHUB_ACTIONS","repository":{"owner":"***-dev","name":"js"},"sha":"33611409b0efd58803be4a96194f5872ddf4bde0","ref":"refs/heads/main","head_ref":"","run":{"workflow":"CI","job":"optimize_ci","run":13041742117}}}
|
|
optimize_ci
Response status: 400
|
|
optimize_ci
***-dev/js/undefined
|
|
optimize_ci
Response returned a non-200 status. Skipping Graphite checks.
|
|
Lint Packages:
apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L163
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/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L170
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/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L177
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/playground-web/src/components/engine/minting/TransactionResults.tsx#L161
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/playground-web/src/components/engine/minting/TransactionResults.tsx#L168
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/playground-web/src/components/engine/minting/TransactionResults.tsx#L175
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/playground-web/src/components/engine/minting/erc1155-mint-to.tsx#L267
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
|