Conversation
|
@dependabot recreate |
Bumps [pip](https://github.com/pypa/pip) from 24.0 to 24.3.1. - [Changelog](https://github.com/pypa/pip/blob/main/NEWS.rst) - [Commits](pypa/pip@24.0...24.3.1) --- updated-dependencies: - dependency-name: pip dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
2148514 to
c207483
Compare
This reverts commit 6be689b.
|
Note: As of pip 24.1+, packages with invalid metadata are now rejected: This follows on from the deprecation warning that pip has been showing since pip 23.2 (released July 2023): If you see pip output mentioning ignoring dependencies due to invalid metadata you will need to upgrade to newer versions of those dependencies. For example, when using Celery versions 5.2.0 and older it is expected that the build will now fail with: Previously (both on Heroku and in your local development environments/CI), pip will have been displaying this deprecation warning: If you use celery, you must upgrade to v5.2.1 (released in 2021) or newer, to pick up this upstream fix: If you are upgrading from Celery 4.x to 5.x, you will need to follow the upgrading steps here: And as always, we recommend keeping your dependencies up to date in general - eg by setting up Dependabot: |
Bumps pip from 24.0 to 24.3.1.
Changelog
Sourced from pip's changelog.
... (truncated)
Commits
05293b6Bump for release6a5db8bMerge pull request #13047 from sbidoul/fix-130467be54ceDon't fail when the same req file is included more than once4f6aeb1Merge pull request #13044 from sbidoul/release/24.3e1b1d51Bump for developmentcdba22fBump for release27f8374Update AUTHORS.txtc79d019Merge pull request #13033 from sbidoul/vendoring-24.3-sbi3ca8921Merge pull request #13041 from sethmlarson/truststore-0.10.00cc7375Upgrade vendored truststore to 0.10.0Dependabot 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)