Skip to content

Releases: capabilityio/capability-token

v0.6.1

20 Nov 12:36
Compare
Choose a tag to compare

Updated dependencies.

v0.6.0

20 Jan 18:29
Compare
Choose a tag to compare

To facilitate detection of Capability Tokens, added the well-known string (ex: CPBLTY) as a property to the non-serialized CapabilityToken object instance. This way, if it is JSON.stringify'ed in its non-serialized form, searching for well-known string will be as effective as when searching for serialized tokens.

v0.5.1

20 Jan 18:28
Compare
Choose a tag to compare

Removed package-lock.json from version control.

v0.5.0

25 Nov 01:55
Compare
Choose a tag to compare

Use JavaScript class syntax.

v0.4.1

21 Aug 12:11
Compare
Choose a tag to compare

Updated dependencies.

v0.4.0

01 Oct 20:35
Compare
Choose a tag to compare

No longer require base64 encoded body when constructing a new CapabilityToken. CapabilityToken can now be constructed with body that is a Buffer or a base64 or base64url encoded String.

Internally, body is now represented as Buffer instead of base64 encoded String.

v0.3.0

01 Oct 20:33
Compare
Choose a tag to compare

Removed extraneous clone dependency.
Updated dependencies.

v0.2.0

28 Jun 21:57
Compare
Choose a tag to compare

When creating a new token, config.body is now optional. If config.body is not specified, the token constructor will now autogenerate token body.

v0.1.0

29 May 23:33
Compare
Choose a tag to compare

Capability token specification and reference implementation.