This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/pip/mypy-0.991
in repository https://gitbox.apache.org/repos/asf/libcloud.git
omit 89153a27b Bump mypy from 0.982 to 0.991
add 121ebe507 Fix typo.
add e2c9614be Reformat the code using isort.
add 003d221e0 Use python 3.7+ syntax for pyupgrade.
add 7fef596ce Bump pyupgrade from 3.1.0 to 3.3.1
add 5462b8643 Merge remote-tracking branch
'remotes/github/dependabot/pip/pyupgrade-3.3.1' into trunk
add 2c0ecc178 Bump paramiko from 2.11.0 to 2.12.0
add bb6f5d0c6 Merge remote-tracking branch
'github/dependabot/pip/paramiko-2.12.0' into trunk
add cdf839986 Bump mypy from 0.982 to 0.991
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (89153a27b)
\
N -- N -- N refs/heads/dependabot/pip/mypy-0.991 (cdf839986)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
libcloud/common/google.py | 8 ++++----
libcloud/test/common/test_google.py | 4 ++--
requirements-lint.txt | 4 ++--
requirements-tests.txt | 2 +-
tox.ini | 14 +++++++-------
5 files changed, 16 insertions(+), 16 deletions(-)
