This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/pip/dev-support/git-jira-release-audit/cryptography-41.0.3
in repository https://gitbox.apache.org/repos/asf/hbase.git
omit 87238d6506c Bump cryptography in /dev-support/git-jira-release-audit
add e3f1a29363a Revert "Bump gitpython in
/dev-support/git-jira-release-audit (#5348)"
add a60c0263c1e HBASE-28019 Bump gitpython in
/dev-support/git-jira-release-audit (#5348)
add 4c2690de60b HBASE-28020 Bump certifi in
/dev-support/git-jira-release-audit (#5333)
add 8ff38e1d926 Bump cryptography in /dev-support/git-jira-release-audit
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 (87238d6506c)
\
N -- N -- N
refs/heads/dependabot/pip/dev-support/git-jira-release-audit/cryptography-41.0.3
(8ff38e1d926)
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:
dev-support/git-jira-release-audit/requirements.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
