chore(deps): bump certifi from 2025.11.12 to 2026.1.4 #447
Conversation
Bumps [certifi](https://github.com/certifi/python-certifi) from 2025.11.12 to 2026.1.4. - [Commits](certifi/python-certifi@2025.11.12...2026.01.04) --- updated-dependencies: - dependency-name: certifi dependency-version: 2026.1.4 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![codecov[bot]](https://avatars.githubusercontent.com/in/254?s=60&v=4){kind=small}
There was a problem hiding this comment.
The change in the files seems to be the update of certifi library version from '2025.11.12' to '2026.1.4'. This is perfectly fine provided that the updated version doesn't introduce any breaking changes that might affect the functionality of the application. Also, the change doesn't reflect whether the application was tested with the new dependency version. Remember, it's always a good practice to run tests after updating a version dependency.
| aenum==3.1.16 ; python_full_version >= "3.9.2" and python_version < "4.0" | ||
| arrow==1.4.0 ; python_full_version >= "3.9.2" and python_version < "4.0" | ||
| certifi==2025.11.12 ; python_full_version >= "3.9.2" and python_version < "4.0" | ||
| certifi==2026.1.4 ; python_full_version >= "3.9.2" and python_version < "4.0" |
There was a problem hiding this comment.
Update seen in certifi version dependency update from '2025.11.12' to '2026.1.4'. Please confirm this new version doesn't present breaking changes that could impact functionality. If not already done, it would be beneficial to run tests on the application with the updated library to ensure no issues are introduced.
There was a problem hiding this comment.
The change seen in this diff only involves updating the version of the 'certifi' library in the 'requirements.txt' file. This is generally a good practice to keep libraries up-to-date and secure, though it depends on if the new library version is compatible with the existing codebase and doesn't break any functionality. No other explicitly code-related problems can be found. Subsequent testing and possible compatibility checks are recommended after such a library update.
| aenum==3.1.16 ; python_full_version >= "3.9.2" and python_version < "4.0" | ||
| arrow==1.4.0 ; python_full_version >= "3.9.2" and python_version < "4.0" | ||
| certifi==2025.11.12 ; python_full_version >= "3.9.2" and python_version < "4.0" | ||
| certifi==2026.1.4 ; python_full_version >= "3.9.2" and python_version < "4.0" |
There was a problem hiding this comment.
You've updated the 'certifi' library to a new version. It's important to run tests to ensure that this update doesn't break any existing functionality in the code. Additionally, be sure to check whether any other dependencies in your configuration might clash with this version of certifi.
Bumps certifi from 2025.11.12 to 2026.1.4.
Commits
c64d9f32026.01.04 (#389)4ac232fBump actions/download-artifact from 6.0.0 to 7.0.0 (#387)95ae4b2Update CI workflow to use Ubuntu 24.04 and Python 3.14 stable (#386)b72a7b1Bump dessant/lock-threads from 5.0.1 to 6.0.0 (#385)ecc2672Bump actions/upload-artifact from 5.0.0 to 6.0.0 (#384)6a897dbBump peter-evans/create-pull-request from 7.0.11 to 8.0.0 (#383)27ca98aBump peter-evans/create-pull-request from 7.0.9 to 7.0.11 (#381)56c59a6Bump actions/checkout from 6.0.0 to 6.0.1 (#382)ae0021cBump actions/setup-python from 6.0.0 to 6.1.0 (#380)ddf5d0bBump actions/checkout from 5.0.1 to 6.0.0 (#378)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)