update dependencies #16113
Triggered via pull request
December 2, 2024 18:49
jnsdls
Status
Cancelled
Total duration
1m 52s
Artifacts
–
CI.yml
on: pull_request
optimize_ci
8s
Build Packages
1m 19s
Lint Packages
1m 17s
Unit Tests
1m 16s
Size
1m 3s
Matrix: E2E Tests
Annotations
32 errors and 8 warnings
|
E2E Tests (pnpm, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (pnpm, esbuild)
The operation was canceled.
|
|
E2E Tests (bun, webpack)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (bun, webpack)
The operation was canceled.
|
|
E2E Tests (npm, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (npm, esbuild)
The operation was canceled.
|
|
E2E Tests (pnpm, webpack)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (pnpm, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (pnpm, webpack)
The operation was canceled.
|
|
E2E Tests (pnpm, vite)
The operation was canceled.
|
|
E2E Tests (yarn, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (yarn, vite)
The operation was canceled.
|
|
E2E Tests (yarn, webpack)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (yarn, webpack)
The operation was canceled.
|
|
E2E Tests (yarn, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (yarn, esbuild)
The operation was canceled.
|
|
Lint Packages
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (bun, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (bun, esbuild)
The operation was canceled.
|
|
Lint Packages
The operation was canceled.
|
|
Build Packages
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
Build Packages
The operation was canceled.
|
|
E2E Tests (bun, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (bun, vite)
The operation was canceled.
|
|
E2E Tests (npm, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (npm, vite)
The operation was canceled.
|
|
E2E Tests (npm, webpack)
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
E2E Tests (npm, webpack)
The operation was canceled.
|
|
Size
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
Size
The operation was canceled.
|
|
Unit Tests
Canceling since a higher priority waiting request for 'CI-refs/pull/5554/merge' exists
|
|
Unit Tests
The operation was canceled.
|
|
optimize_ci
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
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` 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` 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` 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` 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` 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` 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` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|