v0.5.2
registry tool and server improvements
registry
tool improvements:
- YAML I/O is improved to run in parallel for import/export of entire projects.
- YAML I/O supports additional artifact types (apihub extensions, used to add features to the API hub application).
- Registry tool supports two new sub commands,
registry compute score
andregistry compute scorecards
.
registry-server
improvements:
- When the
accept-encoding
header is received and includesgzip
, get spec contents requests return gzipped spec bodies. This allows specs to be stored that exceed the maximum gRPC message size (when uncompressed). It was already possible to upload these specs by sending them gzipped, but prior to this change, the specgetContents
API would always attempt to return uncompressed specs. - When a postgresql create operation fails due to a
unique_key
violation, the API now returns the gRPCAlreadyExists
status. Previously it returnedInternal
, suggesting that that was an internal error inregistry-server
.