chore(master): release 0.5.0 (#151)

Co-authored-by: Adam Uhlíř <[email protected]>

CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## [0.5.0](https://github.com/ethersphere/bee-factory/compare/v0.4.1...v0.5.0) (2022-11-08)
+
+This is a bigger breaking release that brings support for the Bee 1.9. It is not compatible with the earlier Bee's version.
+
+### Features
+
+* increased nodes funding ([#221](https://github.com/ethersphere/bee-factory/issues/221)) ([86e8649](https://github.com/ethersphere/bee-factory/commit/86e86491d460536015425be5f5a91d06e19db694))
+* latest builds ([#150](https://github.com/ethersphere/bee-factory/issues/150)) ([2ef924d](https://github.com/ethersphere/bee-factory/commit/2ef924d615cfc1a612cb9167a28037918114597e))
+* queen image has postage stamp bought ([#220](https://github.com/ethersphere/bee-factory/issues/220)) ([ffbfaa2](https://github.com/ethersphere/bee-factory/commit/ffbfaa2cfa4dc57dd7bc4d1c09debabf450a0d86))
+* supported bee version check ([#223](https://github.com/ethersphere/bee-factory/issues/223)) ([4b02910](https://github.com/ethersphere/bee-factory/commit/4b029108efa70314656e05b10220adf7f0b3958b))
+* update blockchain image and contracts addresses are in labels ([#214](https://github.com/ethersphere/bee-factory/issues/214)) ([a7eb6c6](https://github.com/ethersphere/bee-factory/commit/a7eb6c6d05d35dd44f08e7c3641cf3721a5d9d28))
+
+
+### Bug Fixes
+
+* invalid mode and gas block limit ([#217](https://github.com/ethersphere/bee-factory/issues/217)) ([b8f3039](https://github.com/ethersphere/bee-factory/commit/b8f30398a425be75113056830ff6f4fb787c996b))
+* state generation of docker images ([#216](https://github.com/ethersphere/bee-factory/issues/216)) ([7dc8992](https://github.com/ethersphere/bee-factory/commit/7dc8992df7c92320b7c20c9001b02bd05918d846))
+
 ### [0.4.1](https://www.github.com/ethersphere/bee-factory/compare/v0.4.0...v0.4.1) (2022-05-24)
 
 

README.md

@@ -29,9 +29,11 @@ $ npm install -g @ethersphere/bee-factory
 
 ## Usage
 
+**Starting with Bee Factory's version `0.5.0` it is compatible only with Bee version `1.9.0` and higher!**
+
 ```shell
 # This spins up the cluster for specific Bee version and exits
-$ bee-factory start --detach 1.5.1
+$ bee-factory start --detach 1.9.0
 
 # The spins up the cluster using Bee version configured in external places. See below for options where to place it.
 $ bee-factory start --detach
@@ -45,7 +47,7 @@ $ bee-factory stop
 
 # You can also spin up the cluster without the --detach which then directly
 # attaches to the Queen logs and the cluster is terminated upon SIGINT (Ctrl+C)
-$ bee-factory start 1.5.1
+$ bee-factory start 1.9.0
 ```
 
 For more details see the `--help` page of the CLI and its commands.
@@ -61,7 +63,7 @@ You can omit the Bee version argument when running `bee-factory start` command i
 
 Bee Factory as the NPM package that you can install, like mentioned above, works in a way that it orchestrates launching Bee Factory Docker images
 in correct order and awaits for certain initializations to happen in correct form. These Docker images are automatically built with our CI
-upon every new Bee release, so you can just specify which version you want to run (starting with `1.5.1` version) as part of the `start` command.
+upon every new Bee release, so you can just specify which version you want to run (starting with `1.9.0` version) as part of the `start` command.
 
 If for some reason you want built your own images, that is possible but discouraged and not supported (**here be dragons**) using the scripts in the `generator` subfolder.
 Upon building and publishing these images you can consume them using with Bee Factory with the `--repo` flag.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ethersphere/bee-factory",
-  "version": "0.4.1",
+  "version": "0.5.0",
   "description": "Orchestration CLI for spinning up local development Bee cluster with Docker",
   "keywords": [
     "bee",