gcp-jwt-go icon indicating copy to clipboard operation
gcp-jwt-go copied to clipboard

Moving to maintained golang-jwt/jwt

Open oxisto opened this issue 4 years ago • 11 comments

This PR will move the jwt-go library to the maintained golang-jwt/jwt fork of the jwt-go library, as discussed in http://github.com/dgrijalva/jwt-go/issues/462.

oxisto avatar Jun 09 '21 06:06 oxisto

Are there any plans to merge this?

lazeratops avatar Sep 13 '21 16:09 lazeratops

@lazeratops @oxisto - My sincerest apologies! I'm not sure how I didn't see the notification for this PR. I will make it a point to get this reviewed/merged soon!

someone1 avatar Sep 13 '21 16:09 someone1

Since this will technically be a breaking change, I want to jump onto the latest version of the new repo which is now tagged as v4 (migration guide).

That being said, I'd also have to modify this repo's go module version and deps accordingly (e.g. tagging a v3).

I think we'll want to enhance this PR a little but it's a great start, thank you @oxisto!

someone1 avatar Sep 13 '21 20:09 someone1

Since this will technically be a breaking change, I want to jump onto the latest version of the new repo which is now tagged as v4 (migration guide).

That being said, I'd also have to modify this repo's go module version and deps accordingly (e.g. tagging a v3).

I think we'll want to enhance this PR a little but it's a great start, thank you @oxisto!

Yes, going for the v4 definitely makes sense.

oxisto avatar Sep 14 '21 10:09 oxisto

I finally go around to move this to our current v4 release of jwt-go

oxisto avatar Dec 16 '21 11:12 oxisto

Any update on this PR?

ksimir avatar May 16 '22 03:05 ksimir

I think we just need to bump the go.mod version to v3 so when I merge this and tag it as v3 things work as expected. Also wanted to try this out on some of my projects before merging but I've moved roles since writing this package.

@oxisto / @ksimir - can you confirm if this branch works as intended if you have any production projections you can test this out on?

someone1 avatar May 17 '22 04:05 someone1

Sorry for the late reply, not something in prod but as far as I tested, I didn't see any issue.

ksimir avatar May 31 '22 05:05 ksimir

@someone1 Did you have a chance to try it on your side? I think it's safe to bump to v3 and merge.

ksimir avatar Jun 07 '22 01:06 ksimir

@someone1 Sorry to pile on here, but this would be great if you could get this merged 😄

gmontagu avatar Jun 09 '22 16:06 gmontagu

@someone1 sorry to bump again this discussion but would you mind merging?

ksimir avatar Jul 27 '22 07:07 ksimir