Browse Source

v0.2.2 Alexandria (#1187)

### Added
- Solidity mappings can now have named key and named value types. [seanyoung](https://github.com/seanyoung)

### Changed
- Solang now uses LLVM 15. [LucasSte](https://github.com/LucasSte)
- Solidity on Solana now required the Anchor framework for the client code, and the `@solana/solidity.js`
  Typescript library is no longer compatible with Solidity.
- When casting hex literal numbers into the `bytesN` type, the hex literal may use leading zeros to match the size
with the according `bytesN`, which aligns solang with `solc`. [xermicus](https://github.com/xermicus)

### Fixed
- Many bugs have been fixed by [seanyoung](https://github.com/seanyoung), [LucasSte](https://github.com/LucasSte)
  and [xermicus](https://github.com/xermicus)
- Typos throughout the code have been fixed. [omahs](https://github.com/omahs)

Signed-off-by: Sean Young <sean@mess.org>
Sean Young 2 years ago
parent
commit
2e2e50a771
3 changed files with 10 additions and 12 deletions
  1. 2 4
      CHANGELOG.md
  2. 1 1
      Cargo.toml
  3. 7 7
      docs/installing.rst

+ 2 - 4
CHANGELOG.md

@@ -2,7 +2,7 @@
 All notable changes to [Solang](https://github.com/hyperledger/solang/)
 All notable changes to [Solang](https://github.com/hyperledger/solang/)
 will be documented here.
 will be documented here.
 
 
-## v0.2.2 (unreleased)
+## v0.2.2 Alexandria
 
 
 ### Added
 ### Added
 - Solidity mappings can now have named key and named value types. [seanyoung](https://github.com/seanyoung)
 - Solidity mappings can now have named key and named value types. [seanyoung](https://github.com/seanyoung)
@@ -11,7 +11,7 @@ will be documented here.
 - Solang now uses LLVM 15. [LucasSte](https://github.com/LucasSte)
 - Solang now uses LLVM 15. [LucasSte](https://github.com/LucasSte)
 - Solidity on Solana now required the Anchor framework for the client code, and the `@solana/solidity.js`
 - Solidity on Solana now required the Anchor framework for the client code, and the `@solana/solidity.js`
   Typescript library is no longer compatible with Solidity.
   Typescript library is no longer compatible with Solidity.
-- When casting hex literal numbers into the `bytesN` type, the hex literal may use leading zeros to match the size 
+- When casting hex literal numbers into the `bytesN` type, the hex literal may use leading zeros to match the size
 with the according `bytesN`, which aligns solang with `solc`. [xermicus](https://github.com/xermicus)
 with the according `bytesN`, which aligns solang with `solc`. [xermicus](https://github.com/xermicus)
 
 
 ### Fixed
 ### Fixed
@@ -19,8 +19,6 @@ with the according `bytesN`, which aligns solang with `solc`. [xermicus](https:/
   and [xermicus](https://github.com/xermicus)
   and [xermicus](https://github.com/xermicus)
 - Typos throughout the code have been fixed. [omahs](https://github.com/omahs)
 - Typos throughout the code have been fixed. [omahs](https://github.com/omahs)
 
 
-
-
 ## v0.2.1 Rio
 ## v0.2.1 Rio
 
 
 ### Added
 ### Added

+ 1 - 1
Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 [package]
 name = "solang"
 name = "solang"
-version = "0.2.1"
+version = "0.2.2"
 authors = ["Sean Young <sean@mess.org>", "Lucas Steuernagel <lucas.tnagel@gmail.com>", "Cyrill Leutwiler <bigcyrill@hotmail.com>"]
 authors = ["Sean Young <sean@mess.org>", "Lucas Steuernagel <lucas.tnagel@gmail.com>", "Cyrill Leutwiler <bigcyrill@hotmail.com>"]
 homepage = "https://github.com/hyperledger/solang"
 homepage = "https://github.com/hyperledger/solang"
 documentation = "https://solang.readthedocs.io/"
 documentation = "https://solang.readthedocs.io/"

+ 7 - 7
docs/installing.rst

@@ -28,11 +28,11 @@ Option 2: Download binaries
 
 
 There are binaries available on github releases:
 There are binaries available on github releases:
 
 
-- `Linux x86-64 <https://github.com/hyperledger/solang/releases/download/v0.2.1/solang-linux-x86-64>`_
-- `Linux arm64 <https://github.com/hyperledger/solang/releases/download/v0.2.1/solang-linux-arm64>`_
-- `Windows x64 <https://github.com/hyperledger/solang/releases/download/v0.2.1/solang.exe>`_
-- `MacOS intel <https://github.com/hyperledger/solang/releases/download/v0.2.1/solang-mac-intel>`_
-- `MacOS arm <https://github.com/hyperledger/solang/releases/download/v0.2.1/solang-mac-arm>`_
+- `Linux x86-64 <https://github.com/hyperledger/solang/releases/download/v0.2.2/solang-linux-x86-64>`_
+- `Linux arm64 <https://github.com/hyperledger/solang/releases/download/v0.2.2/solang-linux-arm64>`_
+- `Windows x64 <https://github.com/hyperledger/solang/releases/download/v0.2.2/solang.exe>`_
+- `MacOS intel <https://github.com/hyperledger/solang/releases/download/v0.2.2/solang-mac-intel>`_
+- `MacOS arm <https://github.com/hyperledger/solang/releases/download/v0.2.2/solang-mac-arm>`_
 
 
 Download the file and save it somewhere in your ``$PATH``, for example the bin directory in your home directory. If the
 Download the file and save it somewhere in your ``$PATH``, for example the bin directory in your home directory. If the
 path you use is not already in ``$PATH``, then you need to add it yourself.
 path you use is not already in ``$PATH``, then you need to add it yourself.
@@ -56,7 +56,7 @@ Option 3: Use ghcr.io/hyperledger/solang containers
 
 
 New images are automatically made available on
 New images are automatically made available on
 `solang containers <https://github.com/hyperledger/solang/pkgs/container/solang>`_.
 `solang containers <https://github.com/hyperledger/solang/pkgs/container/solang>`_.
-There is a release `v0.2.1` tag and a `latest` tag:
+There is a release `v0.2.2` tag and a `latest` tag:
 
 
 .. code-block:: bash
 .. code-block:: bash
 
 
@@ -113,7 +113,7 @@ These patches make it possible to generate code for Solana, and fixes
 concurrency issues in the lld linker.
 concurrency issues in the lld linker.
 
 
 You can either download the pre-built libraries from
 You can either download the pre-built libraries from
-`github <https://github.com/hyperledger/solang/releases/tag/v0.2.1>`_
+`github <https://github.com/hyperledger/solang/releases/tag/v0.2.2>`_
 or :ref:`build your own from source <llvm-from-source>`. After that, you need to add the ``bin`` of your
 or :ref:`build your own from source <llvm-from-source>`. After that, you need to add the ``bin`` of your
 LLVM directory to your path, so that the build system of Solang can find the correct version of LLVM to use.
 LLVM directory to your path, so that the build system of Solang can find the correct version of LLVM to use.