celestia-node v0.4.1

This patch release contains a two bug fixes for issues found during testing on v0.4.0.

1. namespaceHasher.Write's error is not properly handled for, so in the case that data comes in that is of an unexpected length, the error is not caught and causes a panic. To remedy that, namespaceHasher.Sum now returns nil in the case that the data is empty such that multihash.encodeHash will catch it and an error will be returned.

2. CoreAccessor used the context passed into it from construction to manage its lifecycle which was incorrect as that context should only be used for the start operation rather than the management of its lifecycle. CoreAccessor now manages its own context internally to the component.

What's Changed

IMPROVEMENTS

• refactor(rpc): move sanity check logic from rpc handlers to implementations. by @HoytRen in https://github.com/celestiaorg/celestia-node/pull/1213

BUG FIXES

• fix: returning nil sum when hasher receives data with incorrect length by @distractedm1nd in https://github.com/celestiaorg/celestia-node/pull/1245
• fix(state): CoreAccessor manages its own context by @renaynay in https://github.com/celestiaorg/celestia-node/pull/1247

MISC

• .github: add triggering on versioned tags by @MSevey in https://github.com/celestiaorg/celestia-node/pull/1237
• refactor(share/ipld): Use consts for node type determination by @renaynay in https://github.com/celestiaorg/celestia-node/pull/1244

Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.4.0...v0.4.1