CHANGELOG.md

@@ -6,6 +6,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 ### Added
+### Changed
+### Removed
+
+## [5.1.0] 2021-05-24
+### Added
 - Child contracts
 - `Chain.clone`
 - `Chain.create`
@@ -292,7 +297,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Simplify calldata creation - instead of passing a compiled contract, simply
   pass a (stubbed) contract string.
 
-[Unreleased]: https://github.com/aeternity/aesophia/compare/v5.0.0...HEAD
+[Unreleased]: https://github.com/aeternity/aesophia/compare/v5.1.0...HEAD
+[5.1.0]: https://github.com/aeternity/aesophia/compare/v5.0.0...v5.1.0
 [5.0.0]: https://github.com/aeternity/aesophia/compare/v4.3.0...v5.0.0
 [4.3.0]: https://github.com/aeternity/aesophia/compare/v4.2.0...v4.3.0
 [4.2.0]: https://github.com/aeternity/aesophia/compare/v4.1.0...v4.2.0

docs/sophia.md

@@ -173,7 +173,7 @@ transaction still only uses up the gas spent running the contract.
 
 #### Contract factories and child contracts
 
-Since the version 5.0.0 Sophia supports deploying contracts by other
+Since the version 5.1.0 Sophia supports deploying contracts by other
 contracts. This can be done in two ways:
 
 - Contract cloning via [`Chain.clone`](sophia_stdlib.md#clone)

rebar.config

@@ -15,7 +15,7 @@
             {base_plt_apps, [erts, kernel, stdlib, crypto, mnesia]}
            ]}.
 
-{relx, [{release, {aesophia, "5.0.0"},
+{relx, [{release, {aesophia, "5.1.0"},
          [aesophia, aebytecode, getopt]},
 
         {dev_mode, true},

src/aesophia.app.src

@@ -1,6 +1,6 @@
 {application, aesophia,
  [{description, "Contract Language for aeternity"},
-  {vsn, "5.0.0"},
+  {vsn, "5.1.0"},
   {registered, []},
   {applications,
    [kernel,