chore(docs): update version history of next/image
#48927
build_and_test.yml
on: pull_request
Determine changes
7s
build-next
/
build
31s
optimize-ci
/
Graphite CI Optimizer
3s
build-native
/
build
25s
validate-docs-links
16s
Matrix: test unit
Waiting for pending jobs
test cargo benches
/
Test
test next-swc wasi
/
build
test devlow package
/
build
Matrix: test prod
Waiting for pending jobs
Matrix: test dev
Waiting for pending jobs
Matrix: test integration
Waiting for pending jobs
Matrix: Test new tests for flakes (dev)
Waiting for pending jobs
Matrix: Test new tests for flakes (prod)
Waiting for pending jobs
Matrix: test ppr dev
Waiting for pending jobs
Matrix: test ppr prod
Waiting for pending jobs
Matrix: test turbopack dev
Waiting for pending jobs
Matrix: test turbopack development integration
Waiting for pending jobs
Matrix: test turbopack production integration
Waiting for pending jobs
Matrix: test turbopack production
Waiting for pending jobs
Matrix: Run devlow benchmarks
Waiting for pending jobs
Matrix: Test new tests when deployed
Waiting for pending jobs
report test results to datadog
0s
thank you, next
0s
Annotations
9 warnings and 10 notices
|
optimize-ci / Graphite CI Optimizer
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Determine changes
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
validate-docs-links
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
ast-grep lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/value/fail_non_local.rs#L8
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_trait_impl.rs#L11
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_static.rs#L8
Don't use a Vc directly in a struct
|
|
no-vc-struct:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_inherent_impl.rs#L11
Don't use a Vc directly in a struct
|
|
thank you, next
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-browser/src/ecmascript/evaluate/chunk.rs#L221
Calling `chunk.ident().to_string().to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L77
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L95
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L105
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L127
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-core/src/reference/mod.rs#L184
Calling `RawModule::new(*source).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-css/src/chunk/mod.rs#L271
Calling `chunk_item_key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/benches/analyzer.rs#L96
Calling `Environment::new(Value::new(ExecutionEnvironment::NodeJsLambda(
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/manifest/chunk_item.rs#L87
Calling `SingleOutputAssetReference::new(*output_asset, key)
|
|
to-resolved-in-loop:
turbopack/crates/turbopack-ecmascript/src/manifest/loader_item.rs#L119
Calling `SingleOutputAssetReference::new(
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
turbo-run-summary-build-native
|
102 KB |
|
|
turbo-run-summary-build-next
|
137 KB |
|
|
turbo-run-summary-lint
|
239 KB |
|
|
turbo-run-summary-types-and-precompiled
|
239 KB |
|