The Neo SPCC team pushed new versions of two NeoFS tools on Oct. 9. The REST Gateway moved to v0.20.0, and the web Panel moved to v0.11.1. Both releases finish the removal of RANGE EACL support and bring the tools in line with the Node v0.57.0 and SDK RC23 batch from Sept. 30. The changes are mostly about reliability, security, and input checks. Not flashy, but useful for anyone running or using NeoFS.
REST Gateway v0.20.0
The REST Gateway acts as an HTTP bridge for apps that talk to NeoFS storage. Version 0.20.0 adds a container revision field to ContainerInfo. That field exposes versioning metadata from Node v0.57.0, so REST clients can see when a container configuration changes.
A clock skew fix deals with v2 session tokens that were rejected when a node’s clock drifted a bit from the issuer’s clock. The gateway also fixes a parsing bug that returned empty rules instead of handling GETRANGEHASH records in container EACL. v0.19.1 had already skipped unsupported operations without crashing, and now the handling is cleaner.
Object uploads with non-numeric __NEOFS__EXPIRATION_EPOCH attributes are rejected with HTTP 400. That stops bad expiration metadata from entering the network. RANGE EACL operation support is gone. The NeoFS SDK Go dependency moved from RC22 to RC23, and other packages like kin-openapi, viper, and grpc were updated too.
Panel v0.11.1
The Panel at panel.fs.neo.org gets compatibility and security work in v0.11.1. It now works with S3 Gateway 0.47.0 and the updated authboxsrv credential service. That follows the S3 credential issuance feature from Panel v0.11.0.
Security changes restrict object previews to safe content types. A prototype pollution bug in the object tree build was fixed. Failed metadata fetches and network error states are handled better.
Wallet and session fixes target everyday use. One fix prevents EACL rule changes during drag-and-drop actions. Token validation now shows signing status for expired tokens and missing permissions. RANGE EACL support was removed here as well. The Docker build image uses Node 22.
Why RANGE EACL is gone
The RANGE EACL removal closes a longer cleanup across NeoFS components. Node v0.57.0 removed the GetRange object service method. SDK RC22 dropped GetRangeHash. The REST Gateway and Panel now remove RANGE from EACL handling because the operation no longer exists in the protocol.
Release notes are available on GitHub for both Panel v0.11.1 and REST Gateway v0.20.0. For node operators and developers, the main takeaway is simple: update to stay aligned with the current storage node and SDK behavior. Older clients may need changes if they still expect RANGE EACL support.
