v0.23.0

Release highlights

This is a 0.22.8-beta.1 pre-release, with old JSON-RPC versions removal.

Added

• RPC metrics now carry a block_target label on rpc_method_calls_total (how a request targeted a block) and an error_kind label on rpc_method_calls_failed_total (the error variant name). The bundled Grafana dashboard (utils/grafana/dashboard.json) gains an expanded JSON-RPC view, and Prometheus recording rules for RPC latency quantiles are provided in utils/prometheus/rpc-recording-rules.yml.

Changed

• JSON-RPC 0.8, 0.7 and 0.6 API support has been removed.
• JSON-RPC API version 0.9 is now served by default on the / path.
• RPC method-call latency is now exported as a Prometheus histogram in seconds, rpc_method_calls_duration_seconds (_bucket/_sum/_count), replacing the summary rpc_method_calls_duration_milliseconds. Update alerts and dashboards to the new name and derive quantiles with histogram_quantile(...) over the _bucket series; see docs/docs/monitoring-and-metrics.md.
• Preconfirmed blocks are now accumulated from the local commit head to the preconfirmed tip, improving RPC latency.

Fixed

• The default --rpc.compiler.concurrency-limit now respects the container's cgroup memory limit instead of the host's total RAM, so it no longer over-provisions compiler concurrency (risking OOM) when running in a memory-limited container.
• starknet_getMessagesStatus now returns failure_reason from the reverted execution status.