Skip to content

next-upgrade: do not add --turbopack flag when --turbo exists in … #15211

next-upgrade: do not add --turbopack flag when --turbo exists in …

next-upgrade: do not add --turbopack flag when --turbo exists in … #15211

Triggered via push October 23, 2024 15:17
Status Success
Total duration 4m 44s
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
2m 2s
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/[email protected]. 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.7 MB
preview-tarballs
65.8 MB
turbo-run-summary-wasm-nodejs
97.6 KB
turbo-run-summary-wasm-web
97.6 KB
turbopack-bytesize-x86_64-unknown-linux-gnu
207 Bytes
wasm-binaries-nodejs
7.74 MB
wasm-binaries-web
7.74 MB