v3.1.1

Patch change

• Added support for the https://schema.inrupt.com/credentials/v2.jsonld JSON-LD context.

Full Changelog: v3.1.0...v3.1.1

v3.1.0

[Deprecation notice]

The following changes are pending, and will be applied on the next major release:

• The status parameter for getAccessGrantAll will default to all rather than granted.

New Feature

• Node 22 is now supported

Bugfix

• The /resources module function have their signature now aligned with the underlying @inrupt/solid-client functions.
  Namely, the options parameter for saveSolidDatasetAt and getSolidDataset support additional entries that were
  already available in @inrupt/solid-client.

Full Changelog: v3.0.5...v3.1.0

v3.0.5

Bugfixes

• Removed base64url dependency due to potential issues with the browser environment.
• A descriptive error is now thrown when trying to create an Access Request/approve an Access Grant for no resource. Previously, such call may not have thrown, but it resulted in an Access Grant granting access to nothing, which would have caused confusion when trying to use it.
• The error thrown when the issuer endpoint for an Access Grant/Request cannot be computed from the provided resource is more comprehensive.

New Contributors

• @garciafdezpatricia made their first contribution in #943
• @RWJMurphy made their first contribution in #965
• @acoburn made their first contribution in #1005

Full Changelog: v3.0.4...v3.0.5

v3.0.4

Bugfixes

• Extend predicate supported by getRequestor: getRequestor now supports the gc:isProvidedToPerson and gc:isProvidedToController
  predicates in addition to the current gc:isProvidedTo predicate.

v3.0.3

Bugfix

• Internal function getConsent is no longer part of the exports, which was causing TS to not build in some setups.

v3.0.2

Bugfix

• getAccessGrantAll no longer includes duplicates in the result set when using a container filtering by resource.

v3.0.1

Bugfixes

• getAccessGrantAll incorrectly excluded non-recursive grants if not filtering on target resource.

v3.0.0

Breaking Changes

• Parsing Access Grants and Access Requests as RDF from JSON-LD: This allows the Access Grants
  and Access Requests to be read using the RDF/JS DatasetCore API. This is a breaking change,
  because their type also now extends the DatasetCore type. Importantly, this dataset is not
  preserved when converting a Verifiable Credential to a string and back doing
  JSON.parse(JSON.stringify(verifiableCredential)). We reccomend that developers set
  returnLegacyJsonld to false in functions such as getAccessGrant in order to avoid
  returning deprecated object properties. Instead developers should make use of the exported
  getter functions to get these attributes.
• Node 16 is no longer supported: The global fetch function is now used instead of
  @inrupt/universal-fetch. This means this library now only works with Node 18 and higher.
• Deprecated signatures removed:
  • denyAccessRequest no longer supports the resourceOwner argument, it must be removed.
  • approveAccessRequest no longer supports the resourceOwner argument, it must be removed.
  • getAccessGrantAll no longer supports the resource argument, which should be merged into
    the params argument along the other AccessParameter.

v3.0.0-alpha.1

New Features

• Support for parsing Access Grants & Access Requests as JSON-LD. This allows them to be read using the RDF/JS DatasetCore API.

v3.0.0-alpha.0

New Features

• Support for parsing Access Grants & Access Requests as JSON-LD. This allows them to be read using the RDF/JS DatasetCore API.