|
1 | 1 | # NEWS |
2 | 2 |
|
3 | | -## next - unreleased |
| 3 | +## 0.23.0 |
| 4 | + |
| 5 | +The Graph Node internals are being heavily refactored to prepare it for the multichain future. |
| 6 | +In the meantime, here are the changes for this release: |
4 | 7 |
|
5 | 8 | - The `GRAPH_ETH_CALL_BY_NUMBER` environment variable has been removed. Graph Node requires an |
6 | | - Ethereum client that support EIP-1898, which all major clients support. |
| 9 | + Ethereum client that supports EIP-1898, which all major clients support. |
7 | 10 | - Added support for IPFS versions larger than 0.4. |
8 | | -- Added Ethereum ABI encoding and decoding functionality #2348. |
| 11 | +- Added Ethereum ABI encoding and decoding functionality [#2348](https://github.com/graphprotocol/graph-node/pull/2348). |
| 12 | +- Experimental support for configuration files, see the documentation [here](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md). |
| 13 | +- Better PoI performance [#2329](https://github.com/graphprotocol/graph-node/pull/2329). |
| 14 | +- Improve grafting performance and robustness by copying in batches [#2293](https://github.com/graphprotocol/graph-node/pull/2293). |
| 15 | + |
| 16 | +### Graphman |
| 17 | +Graphman is a CLI tool to manage your subgraphs. It is now included in the Docker container |
| 18 | +[#2289](https://github.com/graphprotocol/graph-node/pull/2289). And new commands have been added: |
| 19 | +- `graphman copy` can copy subgraphs across DB shards [#2313](https://github.com/graphprotocol/graph-node/pull/2313). |
| 20 | +- `graphman rewind` to rewind a deployment to a given block [#2373](https://github.com/graphprotocol/graph-node/pull/2373). |
| 21 | +- `graphman query` to log info about a GraphQL query [#2206](https://github.com/graphprotocol/graph-node/pull/2206). |
| 22 | +- `graphman create` to create a subgraph name [#2419](https://github.com/graphprotocol/graph-node/pull/2419). |
| 23 | + |
| 24 | +### Metrics |
9 | 25 | - The `deployment_blocks_behind` metric has been removed, and a |
10 | 26 | `deployment_head` metric has been added. To see how far a deployment is |
11 | 27 | behind, use the difference between `ethereum_chain_head_number` and |
12 | | - `deployment_head` |
| 28 | + `deployment_head`. |
| 29 | +- The `trigger_type` label was removed from the metric `deployment_trigger_processing_duration`. |
13 | 30 |
|
14 | 31 | ## 0.22.0 |
15 | 32 |
|
|
0 commit comments