Bump multidict from 4.7.6 to 5.0.0#113
Bump multidict from 4.7.6 to 5.0.0#113dependabot-preview[bot] wants to merge 2 commits intomasterfrom
Conversation
dependabot-preview
bot
added
the
dependencies
|
One of your CI runs failed on this pull request, so Dependabot won't merge it. Dependabot will still automatically merge this pull request if you amend it and your tests pass. |
Bumps [multidict](https://github.com/aio-libs/multidict) from 4.7.6 to 5.0.0. - [Release notes](https://github.com/aio-libs/multidict/releases) - [Changelog](https://github.com/aio-libs/multidict/blob/master/CHANGES.rst) - [Commits](aio-libs/multidict@v4.7.6...v5.0.0) Signed-off-by: dependabot-preview[bot] <[email protected]>
dependabot-preview
bot
force-pushed
the
dependabot/pip/multidict-5.0.0
branch
from
5c785f5 to
16b0a0c
Compare
|
@dependabot close |
|
Leave failures open so we can track unless we're blocking. |
|
Looking into it |
|
Created PR upstream, This should pass as soon as that comes out as it's a transient dependency. |
|
Once upstream fix the issue, we can probably just do away with pinning the dependancy. Once that fix comes out, I'll clean it up. |
|
@dependabot recreate |
|
closing this and will have dependabot recheck for updates |
|
This pull request will no longer be automatically closed when a new version is found as this pull request was created by Dependabot Preview and this repo is using a |
2 participants
Bumps multidict from 4.7.6 to 5.0.0.
Release notes
Sourced from multidict's releases.
Changelog
Sourced from multidict's changelog.
Commits
087f9dcFix artifacts path421de96Fix artifacts path2b22b2cFix manylinux buildeea466dFix tests001ae3bFix spellinge152be0Update whitelista02e976Bump to 5.0.0d41493dBump mypy version9a70da9Drop azure-pipelines integration5fb74cfFinal deploymentDependabot 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.If all status checks pass Dependabot will automatically merge this pull request.
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 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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard: