-
Notifications
You must be signed in to change notification settings - Fork 43k
Use golang-jwt/jwt instead of form3tech-oss/jwt-go #104007
Copy link
Copy link
Closed as not planned
Labels
area/code-organizationIssues or PRs related to kubernetes code organizationIssues or PRs related to kubernetes code organizationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Metadata
Metadata
Assignees
Labels
area/code-organizationIssues or PRs related to kubernetes code organizationIssues or PRs related to kubernetes code organizationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Type
Projects
Status
Closed / Done
We used to have dgrijalva/jwt-go a while ago which was unmaintained. So folks switched to a fork in
form3tech-ossorg. However there is a community maintained fork at https://github.com/golang-jwt/jwt we should be using.Links:
So what do we need to do? Persuade the folks maintaining the following repos to switch to the community fork.
By first filing issues to raise their awareness and following it up with PRs
/area code-organization