RELEASE NOTES - go-i2p/go-i2p
Release notes for: go-i2p Version 0.1.5
This release is only recommended for developers at this time.
The first general-use release will be version 0.2.0
This release resolves issues across the entire codebase. Bugs in the tunnel system were especially widespread and have been the focus of resolution. The code has been extensively refactored to enforce the intended scope of all packages. Ratchet has been factored out of go-i2p and moved to go-noise. Preliminary support for SSU2 is now available.
Release notes for: go-i2p Version 0.1.4
This release is only recommended for developers at this time.
The first general-use release will be version 0.2.0
This release refactors several netDb subsystems to be more flexible when selecting peers. We have implemented congestion cap handling, both honoring remote congestion caps and broadcasting our own congestion state. We have implemented proper reseeding, downloading RouterInfos from multiple sources, verifying TLS and SU3 certificates, to meet the reseed security model. We have fixed dozens of bugs all over the codebase and closed multiple functional gaps.
Release notes for: go-i2p Version 0.1.3
This release is only recommended for developers at this time.
The first general-use release will be version 0.2.0
This release resolves build issues in go-i2p/crypto and brings the library stack into sync.
Release notes for: go-i2p Version 0.1.2
This release is only recommended for developers at this time.
The first general-use release will be version 0.2.0
This release was conducted specifically to test CI/CD pipelines and to bring the library stack in sync.
Release notes for: go-i2p Version 0.1.1
This release is only recommended for developers at this time.
The first general-use release will be version 0.2.0
In version 0.1.1 we officially introduce the lib/embedded API for go-i2p.
This API allows Go developers to simply and straightforwardly include a go-i2p router in their own downstream applications.
This release also corresponds to significant progress in other parts of the namespace, enabled by the new embedded library.
go-i2cpnow functions as a pure-Go I2CP Client library.go-datagramsnow functions as a pure-Go I2P Datagrams librarygo-streamingnow functions as a pure-Go I2P Streaming library- and most importantly,
go-sam-bridgeimplements the SAMv3.3 API, and embeds ago-i2prouter, and is embeddable itself
All these changes are building toward the big API target for go-i2p, which is making I2P integration as simple as possible for Go applications. The latest checkin of onramp now embeds a go-sam-bridge and starts it automatically if SAMv3.3 is not available on the host, meaning that in the next version of onramp, those who upgrade will seamlessly upgrade to having optional embedded I2P routers. Our hope is that it is also possible to do this for the lower-level go-sam-go library as well. Zero-Configuration I2P applications are nearly upon us!