Releases: storj/uplink-c
Releases · storj/uplink-c
v1.4.0
v1.3.0-rc.1
New multipart upload API. New functions for:
- beginning upload
- committing upload
- uploading part
- aborting upload
- listing uploads
- listing upload parts
Known issues:
uplink_part_upload_abort
will not work correctly if uploading part already started.
Based on uplink v1.5.0-rc.1
v1.2.3
Update to Uplink v1.4.6:
- Negative Offset values in DownloadOptions are processed as suffix range requests.
- User-Agent now contains the library version
- ErrBucketNameInvalid is returned if bucket creation fails due to an invalid argument
- The cancel process handler won't issue deletion of the pending object
- Fixed connection leak due to not closing properly connections to satellite
- Fixed downloading of objects with more than 1000 segments
- Fixed downloading of objects that have segments with a different erasure coding scheme
- Encryption keys in access grants are limited to the permission scope of the API key
- Avoid recreating identity and TLS config for every project opening.
- Fix for downloading large files that take more than 1 hour to download.
v1.2.2
- Fix in Access.OverrideEncryptionKey that avoids overriding the wrong node in the encryption store.
- Upgrade uplink to v1.4.4.
v1.2.1: uplink-c: keep go-gpl2.mod up-to-date
This change bumped the https://github.com/storj/uplink dependency from v1.4.1 to v1.4.2.
This change also fixed the GPL2 compatible build mode (which strips out Apache v2 dependencies) to use the same dependency versions as the default build mode (thus upgrading the uplink dependency in GPL2 compatible mode from v1.1.3 to 1.4.2 as well).
v1.2.0
v1.1.0
- API for multi-tenant support in a single app bucket
- New type:
EncryptionKey
represents a key for encrypting and decrypting data. - New function:
derive_encryption_key
derives a salted encryption key for passphrase using the salt. - New function:
access_override_encryption_key
overrides the root encryption key for the prefix in bucket with encryptionKey.
- New type:
- Default dialer now uses
common/socket
BackgroundDialer
. This may result in better congestion control in some environments. In Linux environments, if a congestion controller named 'ledbat' is installed, it will be used. Consider installing https://github.com/silviov/TCP-LEDBAT - Fix for resource leak in uploads.
- Updated to Uplink v1.2.0.
v1.0.5
- Ability to build the library in GPLv2-compatibility mode (see README for instructions).