This is an automated email from the ASF dual-hosted git repository.

dependabot[bot] pushed a change to branch 
dependabot/pre_commit/pre-commit-hooks-63fa582b4b
in repository https://gitbox.apache.org/repos/asf/shiro.git


    omit 351a53d34 chore(deps): bump 
https://github.com/python-jsonschema/check-jsonschema
     add efd594d9a chore(asf.yaml): don't dismiss stale reviews
     add 7d4829cbf *** TEMPORARY *** disable main branch protection
     add a0af4ef9e chore(dependabot): don't update checkstyle for 2.x
     add 0a7a7cf4f chore(deps): bump 
https://github.com/python-jsonschema/check-jsonschema

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   (351a53d34)
            \
             N -- N -- N   
refs/heads/dependabot/pre_commit/pre-commit-hooks-63fa582b4b (0a7a7cf4f)

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:
 .asf.yaml              | 3 +--
 .github/dependabot.yml | 3 +++
 2 files changed, 4 insertions(+), 2 deletions(-)

Reply via email to