Releases: nuts-foundation/nuts-node
Releases · nuts-foundation/nuts-node
v5.4.11
What's Changed
- Fixed an issue where the deactivated status of a DID document could be resolved incorrectly
Full Changelog: v5.4.10...v5.4.11
v5.4.10
v5.4.9
What's Changed
- Disabled darkmode in UI for EmployeeID contract screen by @stevenvegt in #3306
- Clarified logging when existence of private key cannot be determined by @gerardsn in #3305
Full Changelog: v5.4.8...v5.4.9
v5.4.8
What's Changed
- Fixed a VC search bug where certain VCs could no longer be found.
Full Changelog: v5.4.7...v5.4.8
v5.4.7
What's Changed
- Fixed an issue where the node would panic during startup when retrying unfinished private transactions.
- Updated dependencies
Full Changelog: v5.4.6...v5.4.7
Hazelnut update (v5.4.6)
What's Changed
Full Changelog: v5.4.5...v5.4.6
Hazelnut update (v5.4.5)
What's Changed
Full Changelog: v5.4.4...v5.4.5
Hazelnut update (v5.4.4)
What's Changed
Full Changelog: v5.4.3...v5.4.4
Hazelnut update (v5.4.3)
What's Changed
- Fixed an issue where revocations received through the network were not written to a backup that was introduced in v5.4.0.
Nodes upgrading from v5.4.0-v5.4.2 need to make an empty POST call to<node-address>/internal/network/v1/reprocess?type=application/ld+json%3Btype=revocation
. - Reduced number of pages transmitted per message on a full sync to enhance performance
- Fixed a performance issue with initializing the backup databases
- Fixed some typos in NL language templates (@jelmerterwal)
Full Changelog: v5.4.2...v5.4.3
Hazelnut update (v5.4.2)
What's Changed
- Fixed issue where NutsEmployeeCredentials needed to be explicitly trusted when issued by another node by @reinkrul in #2434
Full Changelog: v5.4.1...v5.4.2