NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1352 by repository stars
Latest stable
v1.18.2
Last release 3 years ago
no release in 18 months
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 53 of 53 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
689 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
This small release includes a new accurate reserve size calculation method for the depthmonitor which helps the storage/eviction radius decrease to a
This small release includes a new accurate reserve size calculation method for the depthmonitor which helps the storage/eviction radius decrease to a more accurate value. The depthmonitor change affects the neighborhood size of the pullsync protocol so it is important that node operators upgrade to this version as soon as possible.
This release is a patch release to fix the postage stamp smart contract issues observed on the mainnet. Node operators will need to upgrade as soon as
This release is a patch release to fix the postage stamp smart contract issues observed on the mainnet. Node operators will need to upgrade as soon as possible.
On reboot, nodes will do a full reset of the batchstore and resync batches from the new contract.
expired field to false if batch exists in batchstore. (#3289)The Bee team is excited to announce the latest release which brings the storage incentives a step closer. The first phase of the implementation brings
The Bee team is excited to announce the latest release which brings the storage incentives a step closer. The first phase of the implementation brings the need to upgrade the postage stamp contract. This is going to be a breaking release, meaning that the previous versions of Bee will not be able to connect to the new version of Bee, so node operators will need to upgrade as soon as possible.
One note of caution is that due to the overlay address calculation change, during the initial bootup after the upgrade, old full nodes will go through an overlay migration process, preventing the node from becoming available for some while.
expired property to the stamps queried on the stamps endpoint. This can be used to distinguish between stamps that were just created and the stamps that have expired. (#3162)For a full PR rundown please consult the v1.8.0 milestone.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Due to an unanticipated behavior of library updates that were done in the last release, we are rolling back some of the changes, alongside some signif
Due to an unanticipated behavior of library updates that were done in the last release, we are rolling back some of the changes, alongside some significant bug fixes for the retrieval protocol which has resulted in a protocol logic change that has necessitated a protocol version bump as to prevent possible downturn of the mixed logic in the network. Node operators are requested to update to the latest version as soon as possible. Nodes which are not updated will not be able to retrieve data from the network.
<!-- security concerns, protocol improvements -->
For a full PR rundown please consult the v1.7.0 milestone.
Nothing published for this version
This release is mostly a patch release to fix some issues observed on the mainnet related to high CPU consumption of Bee nodes. Bee client now uses go
This release is mostly a patch release to fix some issues observed on the mainnet related to high CPU consumption of Bee nodes. Bee client now uses go1.18. There are a couple of other fixes also included, please go through the changelog for more information.
chain-enable and swap-endpoint flags. If user provides a swap-endpoint, a separate flag to enable chain is not required. (#3066)/bytes endpoint. (#3044)For a full PR rundown please consult the v1.6.3 milestone.
With the summer solstice behind us, the Bee team is excited to announce the latest release v1.6.2. This release consists of some new features, perform
With the summer solstice behind us, the Bee team is excited to announce the latest release v1.6.2. This release consists of some new features, performance recalibrations and also some bug fixes.
<!-- security concerns, protocol improvements -->
/chainstate endpoint on debug API. This will allow users to query chainstate endpoint during bootstrapping phase to get status of the process. (#3012)/bzz endpoint as http://<CID or ENS>.swarm.localhost:<port>/{path}. This change also adds support for CID resolution to bee. (#2970)/bytes endpoint. Users can use the HEAD request to get content-length of a swarm reference. (#3027)For a full PR rundown please consult the v1.6.2 milestone.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The Bee team is happy to announce the latest release v1.6.1. The release contains a myriad of bug fixes, codebase hardenings, and a few new features.
The Bee team is happy to announce the latest release v1.6.1. The release contains a myriad of bug fixes, codebase hardenings, and a few new features. A particular highlight is the segment inclusion Merkle proofs we've now added that paves the ground for more exciting features coming up in the future.
<!-- security concerns, protocol improvements -->
For a full PR rundown please consult the v1.6.1 milestone.
Nothing published for this version
This latest release is an accumulation of a lot of work done in the last couple of months by the team. We've improved and refactored substantial amoun
This latest release is an accumulation of a lot of work done in the last couple of months by the team. We've improved and refactored substantial amount of components and areas of the codebase as well as fixed a few critical bugs. After deploying this version your node will be forced into a blockchain resync, so please allow it time to sync and in case you're updating several nodes at the same time - make sure to shelf the update in a way that does not cause a lot of them to go offline at the same time due to the long restart time caused by chain syncing. <!-- remove any of the following sections if they do not apply -->
<!-- hopefully none -->
--mainnet=false (#2859)<!-- security concerns, protocol improvements -->
For a full PR rundown please consult the v1.6.0 milestone.
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is a hotfix release over v1.5.0 version, which was released a few weeks back. While testing the release we fixed a few critical issues. A combina
This is a hotfix release over v1.5.0 version, which was released a few weeks back. While testing the release we fixed a few critical issues. A combination of these fixes, the sharky changes and the way we run some of our automated tests, we found an interesting corner case which led to a data race while downloading files from the node. This particular problem will be seen if we overutilise a postage stamp for uploading data and the nodes could parallely be serving data while new data is being uploaded with the same stamp. This has been fixed now and all users are urged to upgrade to the latest version as soon as possible.
e0d56b4 Add extra validation in netstore while retrieving chunks locally. Fallback to retrieving from network if data is not valid. 0b8d10b Ensure correctnes of chunk data from localstore for parallel get/put operations.
For a full PR rundown please consult the v1.5.1 milestone.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.