January 15, 2025
Release Update
Fabric v2.5.11 and v3.0.1 coming soon - updates to dependencies
New work items
February 19, 2025
Release Update
New work items completed
Chaincode batch writes - StartWriteBatch()
Chaincode batch reads - GetMultipleStates()
Planning for a v3.1.0 release
LF Decentralized Trust - Annual Review
Annual Review completed in January
March 19, 2025
Release Update
Fabric v2.5.12 released
Two intermittent panics in gossip component fixed (plus dependency updates)
Fabric v3.1.0 released
New feature - Chaincode batch operations
Release images are pushed to both DockerHub (docker.io) and GitHub Container Registry (ghcr.io) now.
Fabric CA 1.5.14 Issue
The update in Fabric CA v1.5.14 to not use FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3 by default has caused some issues in the community.
Since v1.3.x was 6 years ago we thought there was no need to use the old compatibility mode by default anymore, since it was meant to be a temporary mode, and deployments could still set FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=true if they really needed it.
However, it turns out some components like fabric-operations-console never updated to use the new authorization header, until the recent v1.0.9-33. And in some deployments (e.g. kubernetes operators) it is not straightforward to update environment variables for a managed pod.
If anybody sees issues related to “Invalid token in authorization header: Token signature validation failed" when interacting with Fabric CA server please open an issue.