From 789e69edb0788d7ab10bfa8ce8ac3ffe88517728 Mon Sep 17 00:00:00 2001 From: Nedyalko Andreev Date: Mon, 12 Jul 2021 16:54:38 +0300 Subject: [PATCH] Fix a typo and an omission in the v0.33.0 release notes This should close https://github.com/k6io/k6/issues/2086 --- release notes/v0.33.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/release notes/v0.33.0.md b/release notes/v0.33.0.md index 756a9cf0c81..723d58bf03d 100644 --- a/release notes/v0.33.0.md +++ b/release notes/v0.33.0.md @@ -32,12 +32,12 @@ Load Impact, the company behind k6, was acquired by Grafana Labs! :tada: Nothing - The default end-of-test summary is now completely generated by the same [`k6-summary` JS code](https://jslib.k6.io/k6-summary/0.0.1/index.js) that is hosted on [jslib.k6.io](https://jslib.k6.io/) ([#1975](https://github.com/k6io/k6/pull/1975)). That PR also improved the k6 TTY detection and removed a few Go dependencies and code hacks, though it also caused us to bump the minimum required Go version for compiling k6 to Go 1.16 (because of its usage of [`go:embed`](https://golang.org/pkg/embed/)). - Arrival-rate executors will no longer create a new goroutine for every new iteration ([#1957](https://github.com/k6io/k6/pull/1957) and [#2038](https://github.com/k6io/k6/pull/2038)). - We have enabled GitHub's CodeQL checks for the Go parts of the repo ([#1961](https://github.com/k6io/k6/pull/1961)). Thanks, @jfcg! -- We have added the necessary k6 core changes for providing execution information to scripts [1863](https://github.com/k6io/k6/pull/1863))! This was the groundwork for the extended replacement of the [`__VU` and `__ITER` execution context variables](https://k6.io/docs/using-k6/execution-context-variables/) we plan to introduce. The new API will be able to return other information as well, for example which scenario the current iteration is in, what's the number of the current VU/iteration globally across all k6 instances, or in the current scenario, etc. These APIs are still not available to JS scripts, but we plan to expose them via the [`k6/x/execution` xk6 extension](https://github.com/k6io/xk6-execution) for now and iterate on them in the following weeks, releasing a stable version in k6 v0.34.0. +- We have added the necessary k6 core changes for providing execution information to scripts [#1863](https://github.com/k6io/k6/pull/1863)! This was the groundwork for the extended replacement of the [`__VU` and `__ITER` execution context variables](https://k6.io/docs/using-k6/execution-context-variables/) we plan to introduce. The new API will be able to return other information as well, for example which scenario the current iteration is in, what's the number of the current VU/iteration globally across all k6 instances, or in the current scenario, etc. These APIs are still not available to JS scripts, but we plan to expose them via the [`k6/x/execution` xk6 extension](https://github.com/k6io/xk6-execution) for now and iterate on them in the following weeks, releasing a stable version in k6 v0.34.0. ## Breaking changes - The `k6 cloud` exit code for a failed cloud test was changed from `99` to `97` ([#2046](https://github.com/k6io/k6/pull/2046)). - The default value of `K6_STATSD_TAG_BLOCKLIST` and `K6_DATADOG_TAG_BLACKLIST` is now `vu,iter,url` ([#2063](https://github.com/k6io/k6/pull/2063)). - +- The `__ITER` execution context variable is no longer set in `setup()` and `teardown()` due to [#1863](https://github.com/k6io/k6/pull/1863). This might be better classified as removing a previously undefined behavior instead of a breaking change, but it's still worth mentioning.