Development Roadmap

[oxisto]

Now with v5 landed, we reduced quite some technical debt in the department of the verifier, but let's not stop there. This will serve as a meta-issue detailing the current plans for developing this library. Please note, that development might take a slower pace than others, considering the large number of people depending on this library.

We probably should decide at which point we want to "open" main to v6 changes - possibly still allowing patches to an old v5 branch. Alternatively we could stay on v5 for main for a while and have an experimental v6 branch that is the target of all pull requests that are potentially containing breaking changes.

v5.1

The next iteration of the v5 release can contain everything which is 100 % API compatible.

Bug fixes

• The usual suspects

Quality of life

• Adding canonical Keyfunc functions for RSA, ECDSA, EdDSA and HMAC #275
• Key rotation with VerificationKeySet #344

Performance

• Avoid use of json.NewDecoder #313
• Different PRs already merged in dealing with smaller string performance gains

v6

So for v6, I want to focus on enhancing the developer experience as well as fixing remaining bugs we forgot in v5 that are potentially API breaking.

Bug fixes

• GetID in the Claims interface ? #334
• Return ed25519 key types from their parse functions #324
• Different types for RegisteredClaims before and after JSON marshaling #327

Quality of life

• feat!: add support for type parameter #272
• Add a specific return type / type constraint to Keyfunc and SignedString #337