chore(main): release core 16.0.2 (#199)

🤖 I have created a release *beep* *boop*
---


##
[16.0.2](core-v16.0.1...core-v16.0.2)
(2023-10-12)


### Bug Fixes

* **API:** return correct v value for Legacy tx
([#154](#154))
([ed502ea](ed502ea))
* **API:** U256 for chainId in api::Transaction struct
([#211](#211))
([ca98a1c](ca98a1c))
* **prover:** Fix statistic query
([#193](#193))
([5499093](5499093))
* **state-keeper:** Add L2ToL1LogsCriterion
([#195](#195))
([64459b2](64459b2))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Signed-off-by: Danil <[email protected]>
Co-authored-by: Danil <[email protected]>

.github/release-please/manifest.json

@@ -1,6 +1,6 @@
 {
   "sdk/zksync-web3.js": "0.15.4",
   "sdk/zksync-rs": "0.4.0",
-  "core": "16.0.1",
+  "core": "16.0.2",
   "prover": "7.1.1"
 }

core/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [16.0.2](https://github.com/matter-labs/zksync-era/compare/core-v16.0.1...core-v16.0.2) (2023-10-12)
+
+
+### Bug Fixes
+
+* **API:** return correct v value for Legacy tx ([#154](https://github.com/matter-labs/zksync-era/issues/154)) ([ed502ea](https://github.com/matter-labs/zksync-era/commit/ed502ea9aff50627ae9620f1570579893cbf2722))
+* **API:** U256 for chainId in api::Transaction struct ([#211](https://github.com/matter-labs/zksync-era/issues/211)) ([ca98a1c](https://github.com/matter-labs/zksync-era/commit/ca98a1c70c8482397215221b4e00bdb2edeccd84))
+* **prover:** Fix statistic query ([#193](https://github.com/matter-labs/zksync-era/issues/193)) ([5499093](https://github.com/matter-labs/zksync-era/commit/54990933051632e505c76bd98b83462617cb725a))
+* **state-keeper:** Add L2ToL1LogsCriterion ([#195](https://github.com/matter-labs/zksync-era/issues/195)) ([64459b2](https://github.com/matter-labs/zksync-era/commit/64459b2383a344b558ae648743c3f7d91c1b24c0))
+
 ## [16.0.0](https://github.com/matter-labs/zksync-era/compare/core-v15.1.1...core-v16.0.0) (2023-10-11)
 
 

docs/advanced/01_initialization.md

@@ -2,8 +2,8 @@
 
 The goal of this doc, is to show you some more details on how zkSync works internally.
 
-Please do the dev_setup.md and development.md (these commands do all the heavy lifting on starting the components of
-the system).
+Please do the dev_setup.md and development.md (these commands do all the heavy lifting on starting the components of the
+system).
 
 Now let's take a look what's inside:
 
@@ -23,7 +23,8 @@ As first step, it gets the docker images for postgres and geth.
 Geth (one of the ethereum clients) will be used to setup our own copy of L1 chain (that our local zkSync would use).
 
 Postgres is one of the two databases, that is used by zkSync (the other one is RocksDB). Currently most of the data is
-stored in postgres (blocks, transactions etc) - while RocksDB is only storing the state (Tree & Map) - and it used by VM.
+stored in postgres (blocks, transactions etc) - while RocksDB is only storing the state (Tree & Map) - and it used by
+VM.
 
 Then we compile JS packages (these include our web3 sdk, tools and testing infrastructure).