release notes/v1.0.0-rc2.md
k6 v1.0.0-rc2 is here 🎉!
Continuing our commitment beyond the v1.0.0 release, we are pleased to announce a new release candidate that includes several significant changes:
execution.test.failThe new Binary Provisioning feature automatically requests and uses custom k6 binaries with the required extensions for your tests. This allows you to run scripts that use extensions without manually rebuilding k6 as it was in the past by depending on tools like xk6. The system caches binaries locally for efficiency, and any additional runs with the same dependencies will use the same binary and will run faster.
Binary Provisioning is available for all k6 Cloud users (free and paid plans). It is an experimental feature, it's enabled by opt-in with the feature flag K6_BINARY_PROVISIONING=true.
Binary provisioning is a limited set of extensions that are supported, and it's not available for the k6 run command that might be added in the future. However, local development is supported with the k6 cloud --local-execution command if a cloud token is provided by the canonical login methods.
Check out the documentation for additional details.
execution.test.fail #4672The new execution.test.fail function allows you to explicitly fail a test while letting it continue execution until completion. This gives you more control over test outcomes while still collecting all metrics and completing necessary cleanup tasks.
summaryTrendStats option.pressedKeys being updated concurrently in the browser module.Ended & Interrupted execution states.secretsource also redact float32 and float64 values.internal as preparations for v1.0.0 stabilizationNO_COLOR detection.Set and Map.OpenTelemetry, grpc, golang/x and esbuild dependencies.GetLayoutMetrics.VisualViewport CDP usage.