Skip to content

Do not create client reference manifest for metadata route handlers #13917

Do not create client reference manifest for metadata route handlers

Do not create client reference manifest for metadata route handlers #13917

Triggered via push October 13, 2024 18:20
Status Success
Total duration 4m 15s
Artifacts 7
deploy-target
11s
deploy-target
Matrix: build-wasm
Matrix: build-native
Deploy examples
0s
Deploy examples
Potentially publish release
0s
Potentially publish release
Upload Turbopack Bytesize metrics to Datadog
0s
Upload Turbopack Bytesize metrics to Datadog
Deploy preview tarball
1m 49s
Deploy preview tarball
Release Stats
0s
Release Stats
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
stable - x86_64-unknown-linux-gnu - node@16
The following actions use a deprecated Node.js version and will be forced to run on node20: ijjk/rust-cache@turbo-cache-v1.0.8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
stable - x86_64-unknown-linux-gnu - node@16
Unsupported Cargo.lock format, fallback to caching entire file
stable - x86_64-unknown-linux-gnu - node@16
No files were found with the provided path: .turbo/runs. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size
next-swc-binaries-x86_64-unknown-linux-gnu
43.6 MB
preview-tarballs
65.4 MB
turbo-run-summary-wasm-nodejs
96.5 KB
turbo-run-summary-wasm-web
96.5 KB
turbopack-bytesize-x86_64-unknown-linux-gnu
207 Bytes
wasm-binaries-nodejs
7.73 MB
wasm-binaries-web
7.74 MB