neonewstoday.com
Neo SPCC has released updates for multiple NeoFS components, including the node, REST gateway, S3 gateway, and Panel application. Changes span dynamic block configuration, SDK upgrades, and metadata handling, alongside compatibility with the v2.18 API.
NeoFS node
The latest NeoFS node release, v0.48.0, introduces dynamic block time support for NeoFS networks and full compatibility with API v2.18. The embedded Inner Ring consensus node now supports a max_time_per_block configuration option to make use of the change. Additionally, the Inner Ring now bases epoch ticks on real time rather than block count.
Significant behavioral changes affect SN and IR verification processes. SN no longer signs GET/HEAD responses for requests using API versions newer than v2.17 and verifies proxy responses against headers and checksums.
Write-cache initialization has been optimized, the Metabase no longer stores object headers, and GetRange for FSTree was streamlined. New operations were also added for FSTree, including Head and GetStream.
Several internal services and outdated configurations have been removed, aimed at reducing resource usage and simplifying management. Removed features include short header support in HEAD requests, stuck containers in SN cache, and several deprecated command-line tools. SG-based audit and related fee settings have also been eliminated.
Various bug fixes are included in the release, such as resolution of redundant replication signatures, false negative bootstrap logs, stale epoch issues after RPC disconnection, and data races during write-cache flushing. Object replication now skips containers with inconsistent metadata, and storage node logs have been improved for deletion failures.
NeoFS Panel
NeoFS Panel was migrated to use the Vite build tool and updated to support the searchv2 API in object pagination for its v0.7.0 release.
REST gateway
The upgrade to v0.13.0 of the REST Gateway sees a panic issue in the search v1 endpoint fixed. Configurations have been adjusted to support new peer definitions and renamed settings. Specifically, pool.container_ops_timeout has been renamed to pool.container-ops-timeout, and the peer list format in configuration files now uses array syntax instead of object-based keys.
The gateway also upgraded its NeoFS SDK dependency, bringing compatibility with API v2.18.
Users upgrading from v0.12.0 are advised to rename timeout parameters and update peer lists to the new format to avoid compatibility issues.
S3 gateway
S3 Gateway v0.4.0 corrects a compatibility issue with NeoFS Node v0.48.0 and simplifies internal handling of logs and tags via the __NEOFS__ASSOCIATE attribute.
Follow the official Neo SPCC feed to keep up to date with the latest updates from the team:
https://x.com/neospcc/