Version 1.2

What's Changed

• Update minimum dep to iOS v10 by @frederikbosch in #17
• Allow public init from P384 PublicKey by @frederikbosch in #18
• Work around a backwards compatibility issue in CryptoKit on macOS 13 (et. al) which prevented importing P384 public keys

New Contributors

• @frederikbosch made their first contribution in #17

Full Changelog: 1.1.0...1.2.0

Version 1.1

Summary

Support added for Version 3 Public Paseto tokens (on supportable platforms).

What's Changed

• Update test vectors by @aidantwoods in #15
• Version3 public by @aidantwoods in #14

Full Changelog: 1.0.0...1.1.0

Version 1

Version 1 stable release.

Updates

• Added v3.local, v4.public, v4.local support
• Added support for dealing with nested JSON structures
• Added common validator support

No changes to the underlying crypto in v1/v2.

0.2.1

Should now build on more recent releases of Xcode: circular type definition removed.

Version 0.2.0: Beta

There is lots of internal changes – mostly this should result in changes like writing Message<Encrypted<Version2>> as Message<Version2.Local> and SymmetricKey<Version2> as Version2.SymmetricKey.

To see examples of migration, it may be useful to review this diff, and perhaps the PR #2 also if there is interest into why these changes have occurred.

It's also no longer possible to try to use the "Public" purpose API in version 1 (previously this would throw exceptions or invoke a fatal error since this is not supported – it now just doesn't exist). We now no longer need to create "diverse" types by projecting a type argument to an enum state and alternating behaviour accordingly – instead where different types are required we have used associated types.

Beta v0.1.1

This should be stable enough to start working with. I don't plan on changing the public API too drastically, but we'll see...

We can't really have a stable release until the specification hits v1.0.0 anyway 😉

Beta v0.1

This should be stable enough to start working with. I don't plan on changing the public API too drastically, but we'll see...

We can't really have a stable release until the specification hits v1.0.0 anyway 😉