Merge pull request #2877 from nspcc-dev/chlog-101
CHANGELOG: release 0.101.0
This commit is contained in:
commit
22fc8d1adc
2 changed files with 31 additions and 1 deletions
29
CHANGELOG.md
29
CHANGELOG.md
|
@ -2,6 +2,35 @@
|
|||
|
||||
This document outlines major changes between releases.
|
||||
|
||||
## 0.101.0 "Shortness" (13 Jan 2022)
|
||||
|
||||
This release delivers an important fix for block execution application logs
|
||||
and requires a resynchronization, therefore it's 0.101.0 (even though it's
|
||||
also 3.5.0-compatible). It fixes some other minor problems as well (the other
|
||||
most notable change probably is in the compiler), so we recommend upgrading.
|
||||
|
||||
Improvements:
|
||||
* updated golang.org/x/* dependencies (#2854)
|
||||
* CLI help and required flags handling fixes (#2852)
|
||||
* transfer data storage optimization (#2865)
|
||||
* network's magic number is stored (and checked against the config on
|
||||
startup) in the DB now, reducing potential for node operator errors (#2867)
|
||||
|
||||
Bugs fixed:
|
||||
* in rare cases nodes could request an invalid number of blocks from peers
|
||||
leading to disconnect (#2846)
|
||||
* outdated documentation fixes (#2860, #2876)
|
||||
* application logs for blocks that contained GAS spends for transaction fees
|
||||
contained (and returned from getapplicationlog RPC) incorrect (off by one)
|
||||
values for amount in Transfer events; transaction application logs were not
|
||||
affected by this, but data returned to RPC event subscribers could
|
||||
potentially be (#2865)
|
||||
* findstates RPC returned an error instead of an empty data set for valid
|
||||
contracts that have no data (unlike C# node, #2866)
|
||||
* miscompiled shadowed range loop variable definition (#2871)
|
||||
* missing (compared to C# node) explicit (even though null) 'exception' field
|
||||
in the getapplicationlog RPC output from server (#2872)
|
||||
|
||||
## 0.100.1 "Chaptalization" (28 Dec 2022)
|
||||
|
||||
This is a tiny update that 99.99% of users can easily skip. The reason for
|
||||
|
|
|
@ -7,7 +7,8 @@ functionality.
|
|||
## Versions 0.7X.Y (as needed)
|
||||
* Neo 2.0 support (bug fixes, minor functionality additions)
|
||||
|
||||
## Version 0.100.2 (~February 2022)
|
||||
## Version 0.101.1 (~February 2022)
|
||||
* improved RPC error codes
|
||||
* extended data types for iterators to be used by RPC wrapper generator
|
||||
|
||||
## Version 1.0 (2023, TBD)
|
||||
|
|
Loading…
Reference in a new issue