Merge pull request #1098 from valory-xyz/feat/v0.1.4

Release v0.1.4

.spelling

@@ -165,6 +165,10 @@ v1
 hardcoded
 e2e
 macos
+eg
+frontend
+onchain
+dict
  - docs/index.md
 README.md
 s_
@@ -274,6 +278,7 @@ i
  - HISTORY.md
 0.1.0rc1
 0.1.0rc2
+serializer
  - docs/control_flow.md
 EntryPoint
 StartA

HISTORY.md

@@ -1,5 +1,19 @@
 # Release History - `open-autonomy`
 
+# 0.1.4 (2022-20-08)
+
+Autonomy:
+- Ports deployment resources as data files
+- Adds support for the usage of remote registry when building a service deployment
+- Updates the image build process
+
+Packages:
+- Makes Registration ABCI abstract
+- Adds check to make sure FSM chaining only involves abstract skills
+- Sets a deadline for dict serializer hypothesis test in order to resolve flakiness
+
+Docs:
+- Adds docs on publishing packages
 
 ## 0.1.3 (2022-15-08)
 

SECURITY.md

@@ -8,8 +8,8 @@ The following table shows which versions of `open-autonomy` are currently being
 
 | Version   | Supported          |
 | --------- | ------------------ |
-| `0.1.3`   | :white_check_mark: |
-| `< 0.1.3` | :x:                |
+| `0.1.4`   | :white_check_mark: |
+| `< 0.1.4` | :x:                |
 
 ## Reporting a Vulnerability
 

autonomy/__version__.py

@@ -22,7 +22,7 @@
 __title__ = "open-autonomy"
 __description__ = "A framework for the creation of autonomous agent services."
 __url__ = "https://github.com/valory-xyz/open-autonomy.git"
-__version__ = "0.1.3"
+__version__ = "0.1.4"
 __author__ = "Valory AG"
 __license__ = "Apache-2.0"
 __copyright__ = "2021-2022 Valory AG"

docs/package_publishing.md

@@ -35,7 +35,7 @@ The on-chain protocol form contains:
 - Dependencies of the component (i.e. other components)
 
 After all this details have been filled out and sent, the package will be registered on the on-chain protocol. The component
-owner will receive in his wallet an NFT that represents the ownsership of this component.
+owner will receive in his wallet an NFT that represents the ownership of this component.
 
 It is important to emphasize that two different pushes to IPFS have been
 performed up to this point: the first one, done by the developer to push the code and a second one done through the frontend to push the metadata (that contains the code hash itself).

docs/upgrading.md

@@ -5,6 +5,9 @@ Below we describe the additional manual steps required to upgrade between differ
 
 # Open Autonomy
 
+## `v0.1.3` to `v0.1.4`
+
+This release changes the build process for docker images and service deployments. Refer to documentation for more information.
 
 ## `v0.1.2` to `v0.1.3`
 

tests/test_base.py

@@ -24,4 +24,4 @@
 
 def test_version() -> None:
     """Test the version."""
-    assert autonomy.__version__ == "0.1.3"
+    assert autonomy.__version__ == "0.1.4"