Repository navigation
bump certifi to 2026-10-19 - #191
Merged
Merged
Conversation
zuczkows
approved these changes
Oct 21, 2026
There was a problem hiding this comment.
🔵 Needs a closer look
Dependency pins are consistent, but release availability and artifact hashes remain unverified.
No open issues 🎉
What changed in this PR
Updates certifi from 2026.1.4 to 2026.10.19 across the project's dependency files.
Changes:
- Aligns certifi pins in Pipfile, requirements, and lockfile.
- Updates artifact hashes and the Pipfile lock checksum.
| File | Description |
|---|---|
| requirements.txt | Updates the certifi pin. |
| Pipfile.lock | Updates certifi version, artifact hashes, and lock checksum. |
| Pipfile | Updates the declared certifi version. |
Review effort: Balanced
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.