Merge pull request #2824 from fetchai/fix/package_versions

build: bump package versions

docs/aggregation-demo.md

@@ -19,7 +19,7 @@ Repeat the following process four times in four different terminals (for each {`
 Fetch the aggregator AEA:
 ``` bash
 agent_name="agg$i"
-aea fetch fetchai/simple_aggregator:0.5.3 --alias $agent_name
+aea fetch fetchai/simple_aggregator:0.5.4 --alias $agent_name
 cd $agent_name
 aea install
 aea build
@@ -34,15 +34,15 @@ Create the AEA.
 agent_name="agg$i"
 aea create agent_name
 cd agent_name
-aea add connection fetchai/http_client:0.24.4
-aea add connection fetchai/http_server:0.23.4
-aea add connection fetchai/p2p_libp2p:0.27.3
-aea add connection fetchai/soef:0.27.4
-aea add connection fetchai/prometheus:0.9.4
-aea add skill fetchai/advanced_data_request:0.7.4
-aea add skill fetchai/simple_aggregation:0.3.4
-
-aea config set agent.default_connection fetchai/p2p_libp2p:0.27.3
+aea add connection fetchai/http_client:0.24.5
+aea add connection fetchai/http_server:0.23.5
+aea add connection fetchai/p2p_libp2p:0.27.4
+aea add connection fetchai/soef:0.27.5
+aea add connection fetchai/prometheus:0.9.5
+aea add skill fetchai/advanced_data_request:0.7.5
+aea add skill fetchai/simple_aggregation:0.3.5
+
+aea config set agent.default_connection fetchai/p2p_libp2p:0.27.4
 aea install
 aea build
 ```
@@ -126,8 +126,8 @@ aea config set vendor.fetchai.connections.http_server.config.port $((8000+i))
 
 To publish the aggregated value to an oracle smart contract, add the ledger connection and simple oracle skill to one of the aggregators:
 ``` bash
-aea add connection fetchai/ledger:0.21.3
-aea add skill fetchai/simple_oracle:0.16.3
+aea add connection fetchai/ledger:0.21.4
+aea add skill fetchai/simple_oracle:0.16.4
 ```
 
 Configure the simple oracle skill for the `fetchai` ledger:

docs/aries-cloud-agent-demo.md

@@ -180,7 +180,7 @@ Now you can create **Alice_AEA** and **Faber_AEA** in terminals 3 and 4 respecti
 In the third terminal, fetch **Alice_AEA** and move into its project folder:
 
 ``` bash
-aea fetch fetchai/aries_alice:0.32.3
+aea fetch fetchai/aries_alice:0.32.4
 cd aries_alice
 ```
 
@@ -191,11 +191,11 @@ The following steps create <b>Alice_AEA</b> from scratch:
 ``` bash
 aea create aries_alice
 cd aries_alice
-aea add connection fetchai/p2p_libp2p:0.27.3
-aea add connection fetchai/soef:0.27.4
-aea add connection fetchai/http_client:0.24.4
-aea add connection fetchai/webhook:0.20.4
-aea add skill fetchai/aries_alice:0.26.4
+aea add connection fetchai/p2p_libp2p:0.27.4
+aea add connection fetchai/soef:0.27.5
+aea add connection fetchai/http_client:0.24.5
+aea add connection fetchai/webhook:0.20.5
+aea add skill fetchai/aries_alice:0.26.5
 ```
 </p>
 </details>
@@ -257,14 +257,14 @@ Finally run **Alice_AEA**:
 aea run
 ```
 
-Once you see a message of the form `To join its network use multiaddr 'SOME_ADDRESS'` take note of the address. (Alternatively, use `aea get-multiaddress fetchai -c -i fetchai/p2p_libp2p:0.27.3 -u public_uri` to retrieve the address.) We will refer to this as **Alice_AEA's P2P address**.
+Once you see a message of the form `To join its network use multiaddr 'SOME_ADDRESS'` take note of the address. (Alternatively, use `aea get-multiaddress fetchai -c -i fetchai/p2p_libp2p:0.27.4 -u public_uri` to retrieve the address.) We will refer to this as **Alice_AEA's P2P address**.
 
 ### Faber_AEA
 
 In the fourth terminal, fetch **Faber_AEA** and move into its project folder:
 
 ``` bash
-aea fetch fetchai/aries_faber:0.32.3
+aea fetch fetchai/aries_faber:0.32.4
 cd aries_faber
 ```
 
@@ -275,11 +275,11 @@ The following steps create <b>Faber_AEA</b> from scratch:
 ``` bash
 aea create aries_faber
 cd aries_faber
-aea add connection fetchai/p2p_libp2p:0.27.3
-aea add connection fetchai/soef:0.27.4
-aea add connection fetchai/http_client:0.24.4
-aea add connection fetchai/webhook:0.20.4
-aea add skill fetchai/aries_faber:0.24.3
+aea add connection fetchai/p2p_libp2p:0.27.4
+aea add connection fetchai/soef:0.27.5
+aea add connection fetchai/http_client:0.24.5
+aea add connection fetchai/webhook:0.20.5
+aea add skill fetchai/aries_faber:0.24.4
 ```
 </p>
 </details>

docs/build-aea-programmatically.md

@@ -62,7 +62,7 @@ We will use the stub connection to pass envelopes in and out of the AEA. Ensure
 ```
 
 ## Initialise the AEA
-We use the <a href="../api/aea_builder#aeabuilder-objects">`AEABuilder`</a> to readily build an AEA. By default, the `AEABuilder` adds the `fetchai/default:1.1.5`, `fetchai/state_update:1.1.5` and `fetchai/signing:1.1.5` protocols.
+We use the <a href="../api/aea_builder#aeabuilder-objects">`AEABuilder`</a> to readily build an AEA. By default, the `AEABuilder` adds the `fetchai/default:1.1.6`, `fetchai/state_update:1.1.6` and `fetchai/signing:1.1.6` protocols.
 ``` python
     # Instantiate the builder and build the AEA
     # By default, the default protocol, error skill and stub connection are added

docs/car-park-skills.md

@@ -57,9 +57,9 @@ Install the <a href="https://aea-manager.fetch.ai" target="_blank">AEA Manager</
 
 The following steps assume you have launched the AEA Manager Desktop app.
 
-1. Add a new AEA called `car_detector` with public id `fetchai/car_detector:0.32.3`.
+1. Add a new AEA called `car_detector` with public id `fetchai/car_detector:0.32.4`.
 
-2. Add another new AEA called `car_data_buyer` with public id `fetchai/car_data_buyer:0.33.3`.
+2. Add another new AEA called `car_data_buyer` with public id `fetchai/car_data_buyer:0.33.4`.
 
 3. Copy the address from the `car_data_buyer` into your clip board. Then go to the <a href="https://explore-dorado.fetch.ai" target="_blank">Dorado block explorer</a> and request some test tokens via `Get Funds`.
 
@@ -97,7 +97,7 @@ Follow the <a href="../quickstart/#preliminaries">Preliminaries</a> and <a href=
 
 First, fetch the car detector AEA:
 ``` bash
-aea fetch fetchai/car_detector:0.32.3
+aea fetch fetchai/car_detector:0.32.4
 cd car_detector
 aea install
 aea build
@@ -110,19 +110,19 @@ The following steps create the car detector from scratch:
 ``` bash
 aea create car_detector
 cd car_detector
-aea add connection fetchai/p2p_libp2p:0.27.3
-aea add connection fetchai/soef:0.27.4
-aea add connection fetchai/ledger:0.21.3
-aea add skill fetchai/carpark_detection:0.27.4
+aea add connection fetchai/p2p_libp2p:0.27.4
+aea add connection fetchai/soef:0.27.5
+aea add connection fetchai/ledger:0.21.4
+aea add skill fetchai/carpark_detection:0.27.5
 aea config set --type dict agent.dependencies \
 '{
   "aea-ledger-fetchai": {"version": "<2.0.0,>=1.0.0"}
 }'
-aea config set agent.default_connection fetchai/p2p_libp2p:0.27.3
+aea config set agent.default_connection fetchai/p2p_libp2p:0.27.4
 aea config set --type dict agent.default_routing \
 '{
-  "fetchai/ledger_api:1.1.5": "fetchai/ledger:0.21.3",
-  "fetchai/oef_search:1.1.5": "fetchai/soef:0.27.4"
+  "fetchai/ledger_api:1.1.6": "fetchai/ledger:0.21.4",
+  "fetchai/oef_search:1.1.6": "fetchai/soef:0.27.5"
 }'
 aea install
 aea build
@@ -135,7 +135,7 @@ aea build
 
 Then, fetch the car data client AEA:
 ``` bash
-aea fetch fetchai/car_data_buyer:0.33.3
+aea fetch fetchai/car_data_buyer:0.33.4
 cd car_data_buyer
 aea install
 aea build
@@ -148,19 +148,19 @@ The following steps create the car data client from scratch:
 ``` bash
 aea create car_data_buyer
 cd car_data_buyer
-aea add connection fetchai/p2p_libp2p:0.27.3
-aea add connection fetchai/soef:0.27.4
-aea add connection fetchai/ledger:0.21.3
-aea add skill fetchai/carpark_client:0.27.4
+aea add connection fetchai/p2p_libp2p:0.27.4
+aea add connection fetchai/soef:0.27.5
+aea add connection fetchai/ledger:0.21.4
+aea add skill fetchai/carpark_client:0.27.5
 aea config set --type dict agent.dependencies \
 '{
   "aea-ledger-fetchai": {"version": "<2.0.0,>=1.0.0"}
 }'
-aea config set agent.default_connection fetchai/p2p_libp2p:0.27.3
+aea config set agent.default_connection fetchai/p2p_libp2p:0.27.4
 aea config set --type dict agent.default_routing \
 '{
-  "fetchai/ledger_api:1.1.5": "fetchai/ledger:0.21.3",
-  "fetchai/oef_search:1.1.5": "fetchai/soef:0.27.4"
+  "fetchai/ledger_api:1.1.6": "fetchai/ledger:0.21.4",
+  "fetchai/oef_search:1.1.6": "fetchai/soef:0.27.5"
 }'
 aea install
 aea build
@@ -225,7 +225,7 @@ First, run the car data seller AEA:
 aea run
 ```
 
-Once you see a message of the form `To join its network use multiaddr 'SOME_ADDRESS'` take note of the address. (Alternatively, use `aea get-multiaddress fetchai -c -i fetchai/p2p_libp2p:0.27.3 -u public_uri` to retrieve the address.)
+Once you see a message of the form `To join its network use multiaddr 'SOME_ADDRESS'` take note of the address. (Alternatively, use `aea get-multiaddress fetchai -c -i fetchai/p2p_libp2p:0.27.4 -u public_uri` to retrieve the address.)
 This is the entry peer address for the local <a href="../acn">agent communication network</a> created by the car data seller.
 
 Then, in the car data buyer, run this command (replace `SOME_ADDRESS` with the correct value as described above):

docs/cli-vs-programmatic-aeas.md

@@ -33,7 +33,7 @@ If you want to create the weather station AEA step by step you can follow this g
 Fetch the weather station AEA with the following command :
 
 ``` bash
-aea fetch fetchai/weather_station:0.32.3
+aea fetch fetchai/weather_station:0.32.4
 cd weather_station
 aea install
 aea build

docs/config.md

@@ -24,10 +24,10 @@ connections:                                    # The list of connection public
 - fetchai/stub:0.21.2
 contracts: []                                   # The list of contract public ids the AEA project depends on (each public id must satisfy PUBLIC_ID_REGEX).
 protocols:                                      # The list of protocol public ids the AEA project depends on (each public id must satisfy PUBLIC_ID_REGEX).
-- fetchai/default:1.1.5
+- fetchai/default:1.1.6
 skills:                                         # The list of skill public ids the AEA project depends on (each public id must satisfy PUBLIC_ID_REGEX).
-- fetchai/error:0.18.4
-default_connection: fetchai/p2p_libp2p:0.27.3   # The default connection used for envelopes sent by the AEA (must satisfy PUBLIC_ID_REGEX).
+- fetchai/error:0.18.5
+default_connection: fetchai/p2p_libp2p:0.27.4   # The default connection used for envelopes sent by the AEA (must satisfy PUBLIC_ID_REGEX).
 default_ledger: fetchai                         # The default ledger identifier the AEA project uses (must satisfy LEDGER_ID_REGEX)
 required_ledgers: [fetchai]                            # the list of identifiers of ledgers that the AEA project requires key pairs for (each item must satisfy LEDGER_ID_REGEX)
 default_routing: {}                             # The default routing scheme applied to envelopes sent by the AEA, it maps from protocol public ids to connection public ids (both keys and values must satisfy PUBLIC_ID_REGEX)

docs/connect-a-frontend.md

@@ -3,7 +3,7 @@ This page lays out two options for connecting a front-end to an AEA. The followi
 <img src="../assets/http-integration.jpg" alt="How to connect front-end to your AEA" class="center" style="display: block; margin-left: auto; margin-right: auto;width:80%;">
 
 ## Case 1
-The first option is to create a `HTTP Server` connection that handles incoming requests from a REST API. In this scenario, the REST API communicates with the AEA and requests are handled by the `HTTP Server` connection package. The REST API should send CRUD requests to the `HTTP Server` connection (`fetchai/http_server:0.23.4`) which translates these into Envelopes to be consumed by the correct skill.
+The first option is to create a `HTTP Server` connection that handles incoming requests from a REST API. In this scenario, the REST API communicates with the AEA and requests are handled by the `HTTP Server` connection package. The REST API should send CRUD requests to the `HTTP Server` connection (`fetchai/http_server:0.23.5`) which translates these into Envelopes to be consumed by the correct skill.
 
 ## Case 2
-The second option is to create a front-end comprising a stand-alone `Multiplexer` with a `P2P` connection (`fetchai/p2p_libp2p:0.27.3`). In this scenario the <a href="../acn">Agent Communication Network</a> can be used to send Envelopes from the AEA to the front-end.
+The second option is to create a front-end comprising a stand-alone `Multiplexer` with a `P2P` connection (`fetchai/p2p_libp2p:0.27.4`). In this scenario the <a href="../acn">Agent Communication Network</a> can be used to send Envelopes from the AEA to the front-end.

docs/connection.md

@@ -36,7 +36,7 @@ The developer needs to implement four public coroutines:
 
 - The `receive` coroutine is continuously called by the AEA framework. It either returns `None` or an envelope. The `receive` coroutine must implement the logic of data being received by the agent, and if necessary, its translation into a relevant protocol.
 
-The framework provides a demo `stub` connection which implements an I/O reader and writer to send and receive messages between the agent and a local file. To gain inspiration and become familiar with the structure of connection packages, you may find it useful to check out `fetchai/stub:0.21.2`, `fetchai/http_server:0.23.4` or `fetchai/http_client:0.24.4` connections. The latter two connections are for external clients to connect with an agent, and for the agent to connect with external servers, respectively.
+The framework provides a demo `stub` connection which implements an I/O reader and writer to send and receive messages between the agent and a local file. To gain inspiration and become familiar with the structure of connection packages, you may find it useful to check out `fetchai/stub:0.21.2`, `fetchai/http_server:0.23.5` or `fetchai/http_client:0.24.5` connections. The latter two connections are for external clients to connect with an agent, and for the agent to connect with external servers, respectively.
 
 ### Primary methods to develop - sync connection interface