v0.8.0-beta.1

New Features

• Support for parsing Verifiable Credentials as JSON-LD. This allows the Verifiable Credential to be read using the RDF/JS DatasetCore API.

v0.7.4

Internal Changes

• Remove some assumptions for an end-to-end test. This should be transparent to dependants.

v0.7.3

Internal Changes

• Remove some assumptions for an end-to-end test. This should be transparent to dependants.

v0.8.0-beta.0

New Features

• Support for parsing Verifiable Credentials as JSON-LD. This allows the Verifiable Credential to be read using the RDF/JS DatasetCore API.

v0.8.0-alpha.0

New Features

• Support for parsing Verifiable Credentials as JSON-LD. This allows the Verifiable Credential to be read using the RDF/JS DatasetCore API and also improves normalization of Verifiable Credentials that are returned within library.

v0.7.2

• Build system (bundler and TypeScript) updates. This should be transparent to dependants.

v0.7.1

Bugfix

• Fix broken checks for null fields

v0.7.0

New features

• Node 20 support

v0.6.0

New features

• Node 18 is now supported
• A new function isValidVerifiablePresentation has been added to the verify module, which verifies the validity of a VP using a verification service.
• getVerifiableCredentialApiConfiguration now discovers the future-compatible
  specification-compliant endpoints, as well as the legacy endpoints.
• A query function is added from the top-level export and the @inrupt/solid-client-vc/query submodule. It implements the Verifiable Presentation Request mechanism as described in https://w3c-ccg.github.io/vp-request-spec/. An important note is that we make the assumption that an endpoint supporting Verifiable Presentation Request is available at a /query path, which is outside of the VC API specification scope. This assumption is used to distinguish new endpoints vs legacy endpoints. Currently, only Query by Example VPRs are supported, which is similar to the legacy behavior in a lot of ways. The existing getVerifiableCredentialAllFromShape function now supports both legacy and VPR-compliant endpoints.

Other changes

• Upgraded documentation tooling and improved documentation output.
• Added named exports to revoke, verify, and derive (these were previously default exports but they format poorly in the documentation)