Skip to content

[DASH-605] Add profile OG image (#5775) #17129

[DASH-605] Add profile OG image (#5775)

[DASH-605] Add profile OG image (#5775) #17129

Triggered via push December 17, 2024 17:00
Status Success
Total duration 2m 13s
Artifacts

CI.yml

on: push
optimize_ci
3s
optimize_ci
Matrix: E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

27 warnings
optimize_ci
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
optimize_ci
Request body: {"token":"***","caller":{"name":"graphite-ci-action","version":"0.0.0"},"context":{"kind":"GITHUB_ACTIONS","repository":{"owner":"***-dev","name":"js"},"sha":"6e2e426be6976c00ce34354d0ae6b38bce4d1a2c","ref":"refs/heads/main","head_ref":"","run":{"workflow":"CI","job":"optimize_ci","run":12377776327}}}
optimize_ci
Response status: 400
optimize_ci
***-dev/js/undefined
optimize_ci
Response returned a non-200 status. Skipping Graphite checks.
Build Packages
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (pnpm, vite)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (npm, esbuild)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (npm, vite)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (bun, vite)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (pnpm, webpack)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (bun, webpack)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (npm, webpack)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (pnpm, esbuild)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Unit Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (bun, esbuild)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (yarn, esbuild)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (yarn, vite)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (yarn, webpack)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Lint Packages
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` 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