fix: restore cryptography dependency to requirements.txt (#13055) - #13056
fix: restore cryptography dependency to requirements.txt (#13055)#13056RsbhThakur wants to merge 1 commit into
Conversation
…hive#13055) Restores cryptography==44.0.2 to requirements.txt (alphabetically under beautifulsoup4).
|
Thank you @RsbhThakur for this PR! Welcome to Open Library — great to have you contributing! 🤖 Copilot has been assigned for an initial review. The linked issue (#13055) has been triaged (Priority: 1). A reviewer must first be assigned. There are currently 100+ open non-draft PRs ahead of yours in the queue, though the Priority: 1 label means this should be picked up promptly. PR triage checklist (maintainers / Richy)
Note This comment was automatically generated by PAM, Open Library's Project AI Manager. PAM provides status visibility, performs basic project management functions, and gives actionable feedback so contributors aren't left waiting. |
|
Hi @mekarpeles, I noticed the cryptography fix has just been merged as part of the rebase cleanup in #13063. Since the issue is resolved now, I'll close this PR. Glad to see it sorted out! |
Restores cryptography==44.0.2 to requirements.txt (alphabetically under beautifulsoup4).
Closes #13055
fix
Technical
cryptography.fernet.Fernetand pinningcryptography==44.0.2inrequirements.txt.requirements.txtdiff accidentally omitted/removedcryptography==44.0.2during dependency updates.openlibrary/accounts/model.pyare still live, meaning fresh environments or clean builds that pull dependencies fromrequirements.txtcrash with aModuleNotFoundErroron/account/login.cryptography==44.0.2requirement alphabetically.Testing
docker compose build --no-cache && docker compose up -dhttp://localhost:8080/account/loginand verify that the page loads and login succeeds smoothly.Screenshot
N/A (Backend dependency fix. Traceback screenshot is available in #13055)
Stakeholders
@mekarpeles