Releases: bytecodealliance/registry
Releases · bytecodealliance/registry
v0.4.2
What's Changed
- Reverted ci publish by @calvinrp in #260
- Add warning field to fetch logs response. by @RobbieMcKinstry in #262
- package namespace and name validation enforces lowercase only by @calvinrp in #265
- Bump h2 from 0.3.24 to 0.3.26 by @dependabot in #267
- Bump whoami from 1.4.1 to 1.5.1 by @dependabot in #266
- Simplifying the client API and refactoring federation by @calvinrp in #268
- Improved package init and publish flow by @calvinrp in #269
- fix for linux keyring issues by @calvinrp in #270
New Contributors
- @RobbieMcKinstry made their first contribution in #262
Full Changelog: v0.4.1...v0.4.2
v0.4.1
v0.4.0
- added
warg login
to client to provide registry authentication token - improved client federation usability with namespace mapping to registry, set a default signing key to be used across registries and added
Warg-Registry-Hint
header #246 - removed temporary serde struct field alias #221
- refactored keyring management into its own crate
warg-credentials
, making it easier for other projects such ascargo-component
to use - replaced
HashMap
/HashSet
withIndexMap
andIndexSet
- dependency security version bump for
mio
per dependabot recommendation - added capability to use vendored openssl
v0.3.0
PackageId
renamedPackageName
- Added fetch package names endpoint
- Added fetch registry ledger sources endpoint
- Added verify registry checkpoint endpoint
- For federation, added to the operator log namespace defined by the registry as well as imported namespaces from another registry
- For federation, added
Warg-Registry
header to indicate the subject registry that the server should respond as if it was that registry - Bug fix in the client CLI unnecessarily requesting consistency proof when the log length was unchanged and errors if the log length goes backward
- Updated dependencies to newer versions
- Bug fix for LogState rollback not implemented correctly #242
v0.2.0
Changes
- Fixed missing
serde(flatten)
for package record status response onPOST /v1/package/{logId}/record
andGET /v1/package/{logId}/record/{recordId}
endpoints; - Fetch logs
POST /v1/fetch/logs
endpoint generalized the cursor value for operator and package logs from aRecordId
string hash to afetch_token
as an implementation-defined string; The reference implementation still uses theRecordId
as thefetch_token
; - Added Protobuf serialization/deserialization for Stack Log and Vec Log;
- Added
AnyHash::new()
; - Added
impl From<RecordId> for AnyHash
andimpl AsRef<[u8]> for RecordId
; - Changed
from_protobuf(bytes: Vec<u8>)
tofrom_protobuf(bytes: &[u8])
forProtoEnvelope
; - Added
warg reset
command to clear local cache of registry log data; - Added
warg clear
command to clear local cache of content downloads; - Added
GET /v1/content/{digest}
endpoint for getting content source download URLs and simplifiedGET /v1/package/{logId}/record/{recordId}
endpoint to be used for polling the record status after publishing; - Upload HTTP URLs can now specific the
method
andheaders
, so that can usePOST
orPUT
as well asAuthorization
andContent-Type
headers; - Download HTTP URLs can specify whether the
Range
header is supported to download pieces of large files in parallel; Optionalsize
field is provided for the expected file size; - Fix so that the client CLI verifies the
TimestampedCheckpoint
signature when updating checkpoints;
v0.1.0
What's Changed
First release of the warg crates 🎉
Full Changelog: https://github.com/bytecodealliance/registry/commits/v0.1.0