This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/pip/pylint-2.15.4
in repository https://gitbox.apache.org/repos/asf/libcloud.git
discard 69d2190fe Bump pylint from 2.15.3 to 2.15.4
add 7d2c879c4 Bump astroid from 2.12.10 to 2.12.11
add b9e37f2d8 Merge pull request #1783 from
apache/dependabot/pip/astroid-2.12.11
add eaab3a96c Bump pylint from 2.15.3 to 2.15.4
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 (69d2190fe)
\
N -- N -- N refs/heads/dependabot/pip/pylint-2.15.4 (eaab3a96c)
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:
requirements-lint.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
