Minimal Update to JWTKit 5

[dimitribouniol]

Based on #14, here is the minimal set of changes to move this over to JWTKit 5. As this library is likely blocking adoption for many upstream projects, I'm hoping this can accelerate the process before more full-fledged support can be added from #14.

[dimitribouniol]

If the main concern is changing the major version dependency from 4 to 5, vapor/jwt-kit#221 will help add additional support that this library in particular can use to remain backwards compatible with version 4 while also supporting 5.

[alexanderjordanbaker]

@dimitribouniol Thank you for this submission, was waiting for a release with breaking changes to put this into, this looks good!

[dimitribouniol]

Would finishing the compatibility update for jwt-kitv4 help get this in sooner then? This way it won’t require a release with breaking changes. If so, I can prioritize getting that finished this week.

[alexanderjordanbaker]

@dimitribouniol

error: Dependencies could not be resolved because 'jwt-kit' >= 5.0.0 contains incompatible tools version (6.0.0) and root depends on 'jwt-kit' 5.0.0..<6.0.0.

Looks like this is not possible on its own, it requires Swift 6

[dimitribouniol]

I’ll get that compatibility layer in then - this way we can keep the version locked to the latest v4 patch in Package.swift, and we can have a Package-swift6.0.swift that uses jwt-kit v4-5. I think that should cover all our bases?

(this code in the PR will incidentally stay the same since the compatibility layer adds the new v5 API surface to the v4 version branch)

[alexanderjordanbaker]

@dimitribouniol We are upgrading the library to Swift 6 as part of this breaking change, and after doing so tests are passing

[dimitribouniol]

That works too haha

[dimitribouniol]

While I have you re: breaking changes, this would also be a good one to consider addressing: #52

[alexanderjordanbaker]

It’s in my local branch already, just have to push it out

[dimitribouniol]

Sweet, thanks for the updates!