Bump version to v0.26.1 and prepare the release notes

README.md

@@ -147,7 +147,7 @@ There are two reasons for this. The first is, of course: performance. If you rea
 
 But there's another, more interesting reason. By forcing all imports and file reads into the init context, we design for distributed execution. We know which files will be needed, so we distribute only those files to each node in the cluster. We know which modules will be imported, so we can bundle them up in an [archive](https://docs.k6.io/docs/archives-for-bundling-sharing-test) from the get-go. And, tying into the performance point above, the other nodes don't even need writable file systems - everything can be kept in-memory.
 
-This means that if your script works when it's executed with `k6 run` locally, it should also work without any modifications in a distributed execution environment like `k6 cloud` (that executes it in the Load Impact cloud infrastructure) or, in the future, with the [planned](https://github.com/loadimpact/k6/wiki/Roadmap) k6 native cluster execution mode.
+This means that if your script works when it's executed with `k6 run` locally, it should also work without any modifications in a distributed execution environment like `k6 cloud` (that executes it in the commercial [k6 cloud infrastructure](https://k6.io/cloud)) or, in the future, with the [planned](https://github.com/loadimpact/k6/wiki/Roadmap) k6 native cluster execution mode.
 
 ### Script execution
 

lib/consts/consts.go

@@ -8,7 +8,7 @@ import (
 )
 
 // Version contains the current semantic version of k6.
-var Version = "0.26.0" //nolint:gochecknoglobals
+var Version = "0.26.1" //nolint:gochecknoglobals
 
 // VersionDetails can be set externally as part of the build process
 var VersionDetails = "" // nolint:gochecknoglobals

release notes/v0.26.1.md

@@ -0,0 +1,12 @@
+k6 v0.26.1 is here! This is a minor release that supports the rebranding of LoadImpact to k6, the new [k6.io website](https://k6.io/), and the new [k6 cloud service](https://k6.io/cloud)! :tada:
+
+In practical terms, all that it means for k6 is that the URLs for cloud tests will point to https://app.k6.io, instead of https://app.loadimpact.com. The old URLs (and old k6 versions) will still continue to work - for the next 3 months the old app and the new one would work in parallel, and after that period the old app will redirect to the new one. Nothing changes in regards to the k6 open source project and our commitment to it!
+
+You can find more information about the rebranding in our blog post about it: https://k6.io/blog/load-impact-rebranding-to-k6
+
+# Changes in this release compared to v0.26.0:
+
+* Fix how HTTP request timeouts are specified internally. This is not a bug in current k6 releases, it only affects k6 if it is compiled with Go 1.14, which at this time is still not officially released. (#1261)
+* Improve the official docker image to use an unprivileged user. Thanks, @funkypenguin! (#1314)
+* Fix the unintentional sharing of `__ENV` between VUs, which could result in data races and crashes of k6. (#1329)
+* Update cloud URLs to point to https://app.k6.io instead of https://app.loadimpact.com. (#1335)