Skip to content

Fix PyJWT migration: use PyJWTError handler and update stale docstrings#4920

Closed
Copilot wants to merge 2 commits intounicron-4452-vulns-from-code-scanning-toolsfrom
copilot/sub-pr-4919
Closed

Fix PyJWT migration: use PyJWTError handler and update stale docstrings#4920
Copilot wants to merge 2 commits intounicron-4452-vulns-from-code-scanning-toolsfrom
copilot/sub-pr-4919

Conversation

Copy link

Copilot AI commented Mar 3, 2026

Two issues left over from the python-josePyJWT migration:

  • cla/user.py: PyJWTError was imported but never used — the catch block was still except Exception, masking non-JWT errors. Changed to except PyJWTError so unexpected failures propagate.
  • cla/controllers/github_application.py: GithubCLAIntegration docstrings still claimed python-jose was in use. Updated both class and method docstrings to reflect actual PyJWT usage.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

…cation.py docstrings

Co-authored-by: lukaszgryglicki <2469783+lukaszgryglicki@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix vulnerabilities in backend dependencies Fix PyJWT migration: use PyJWTError handler and update stale docstrings Mar 3, 2026
@lukaszgryglicki
Copy link
Member

Closing, I've actually did similar changes to the original PR myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants