v6.2.0

6.2.0 (2023-08-03)

Features

• add new redistribution state properties (#862) (c049101)

v6.1.0

6.1.0 (2023-08-01)

Features

• add http adapter option to bee and bee debug (#860) (ff78e0d)

v6.0.0

6.0.0 (2023-05-22)

• Adds streaming upload support for single files
• Fixes a segmentation fault when running tests in a project where bee-js is a dependency
• Fixes incompatibilities between Node versions 16, 18 and 19
• Fixes an issue with directory and website uploads, where the resulting tar file had more zero-byte padding than standard, causing a connection reset from Bee’s side
• Fixes a bug where projects could not be installed as root where bee-js is a dependency
• Fixes a bug related to code splitting, causing frontend projects built with webpack not being able to fully load bee-js
• Can now be built with slim Docker images, Python is no longer a dependency during project build

⚠ BREAKING CHANGES

• change http library (#842)

Features

• change http library (#842) (e5f0b35)

v5.2.0

5.2.0 (2023-02-20)

Features

• add redistribution state endpoint (#834) (7715c99)

v5.1.2

5.1.2 (2023-01-31)

This release updates Ky (the http library) and restructures its internal usage in order to keep the backward compatibility with CommonJS builds.

v5.1.1

5.1.1 (2022-12-21)

This is small release that brings compatibility with Bee 1.10.0 release.

Bug Fixes

• backward compatibility for wallet ep (#803) (63d7aed)
• staking ep url change (#804) (63d7aed)

v5.1.0

5.1.0 (2022-11-11)

This is a smaller release that brings support for Bee 1.9 and several smaller features.

Features

• add readiness endpoint (#787) (03e2694)
• staking endpoint support (#793) (f584c89)

v5.0.0

5.0.0 (2022-07-28)

This is a breaking release that brings support for Bee 1.7 and cleans up some long awaiting breaking changes that we had lined up:

• We have removed interfaces DebugPostageBatch (for PostageBatch) and NodesInfo (for NodeInfo).
• We have changed the cid property of the UploadResultWithCid interface to be a function instead of getter as this property is not available for encrypted references which caused some troubles when serializing the whole object.
• We have enabled by default waiting for the newly created postage batches to be usable (originally the waitForUsable property of the BeeDebug.createPostageBatch() defaulted to false, now it is true).
• We have added support for the Bee. createFeedManifest() to return object instead of directly reference that also has support for getting CID with the .cid() function.

⚠ BREAKING CHANGES

• enable waiting for postage batch to be usable by default (#746)
• adds support for Feed Manifest CID (#745)
• drop node 12 support (#741)
• drop DebugPostageBatch in favor of PostageBatch inteface (#743)
• drop NodesInfo in favor of NodeInfo inteface (#742)
• convert cid getter to function (#740)

Features

• adds support for Feed Manifest CID (#745) (37c5b55)
• enable waiting for postage batch to be usable by default (#746) (cb05d22)

Bug Fixes

• convert cid getter to function (#740) (0b46862)

Code Refactoring

• drop DebugPostageBatch in favor of PostageBatch inteface (#743) (3f66764)
• drop NodesInfo in favor of NodeInfo inteface (#742) (acddb14)

Miscellaneous Chores

• drop node 12 support (#741) (f79eb3f)

v4.1.1

4.1.1 (2022-05-26)

This is a hotfix release to our build setup that published bee-js with a broken package structure.

Bug Fixes

• move sleep to have all code in src (#696) (19171cc)

v4.1.0

4.1.0 (2022-05-24)

Shortly after the last release, we bring you another release that brings some nice improvements and new features together with some fixes.

✅ Node 18

We have verified the support for Node 18. It introduces a native implementation of fetch API that we use as HTTP client. This implementation wraps the errors that it throws into a nested Error object, so we unwrap these errors for better error handling.

⏳ Waiting for postage stamps to be usable

When a postage stamp is created the (BeeDebug.createPostageStamp() method is called), Bee creates an on-chain transaction that creates this transaction in the smart contract, but the stamp is not immediately "usable" as Bee waits for several blockchain blocks in order to be sure that the postage stamp won't disappear from the blockchain. During this period Bee won't accept this stamp and will return the error stamp is not usable. After this period Bee pronounces it as usable and the users can upload content using it.

In most use cases, when you create the postage stamp you want to actually wait until the stamp is usable and only then return it to the user. For that, you had to implement your own waiting logic, but no more!

The BeeDebug.createPostageStamp() method has a new option waitForUsable which if specified, then the Promise this method returns is resolved only after the Bee confirms the postage stamp to be usable. Be aware that if used, then the call time of this method raises dramatically!

In the next breaking release this option will be turned on, by default!

🔐 Wallet endpoint support

The Bee 1.6.0 release introduced /wallet endpoint that exposes the balance of the node's wallet and some other related metrics. In this release we add support for this endpoint.

Features

• cids support (#681) (02d8f9c)
• expose underlying undici error messages (#694) (b164b70)
• support for waiting on stamp to be usable (#678) (f675dc3)
• wallet endpoint support (#683) (2af84c0)

Bug Fixes

• modify the ENS validation to work in safari or older browsers (#687) (2e172fb)
• no invalid amount for stamps (#682) (b2697d5)