Skip to content
This repository has been archived by the owner on Feb 11, 2025. It is now read-only.

v0.3.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@thomastaylor312 thomastaylor312 released this 03 Feb 20:19
v0.3.0
ecaec5e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This is the 0.3 feature release for Bindle. This release was mostly focused on some underlying optimization and some bug fixes. There was also a new section added on bindle signing to the specification

Installing

You can download the prebuilt binaries for the Bindle CLI client, the Bindle server, and 2 helper CLI tools from the following links:

Once downloaded, you can follow the installation and getting started instructions

Using as a crate

Besides the pre-compiled binaries, we also publish a fully featured crate (that the binaries also use). You can find docs here.

Caveats

Please note that this is NOT production-ready software, but it is in a usable/consumable state. Because this is pre-1.0 software, we make no guarantees about spec, Rust API, or CLI compatibility. However, we will do our best to call out every breaking change in future release notes. Once we hit 1.0, backwards compatibility guarantees will be in effect.

Major Features

  • There is now an LRU cache implementation available in the SDK
  • The Bindle spec has been updated with information on how to sign Bindles. This part of the spec is still under development and may undergo a few more changes. The Invoice object now has methods for signing bindles.

Bug Fixes

  • This release contains one major bug fix for a possible race condition with the built in FileProvider if 2 people tried to create a resource at the same time or if one tried to read while the other writes. We also updated the documentation of the Provider trait to reflect the need for locking/atomic operations when implementing a terminal Provider

Known Issues/Missing Features

  • The standalone bindle implementation does not currently handle tarballs. This will be added in a future release
  • The signing and verification code has not been integrated into the Bindle server or API. This will be added for the 0.4 release

Breaking Changes

There were no major breaking changes in this release

What's next?

Our next anticipated version is 0.4.0 (although we will cut a 0.3.1 if necessary). Our main focus for 0.4 will be around implementing signing validation on the server. Please give things a try and feel free to open PRs or issues with your feedback. In fact, your feedback is crucial as we continue to solidify the spec and features desired in Bindle!

Assets 2
Loading