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

github-bot pushed a change to branch 
dependabot/maven/commons-io-commons-io-2.14.0
in repository 
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-sightly-compiler.git


    omit 9782e10  Bump commons-io:commons-io from 2.5 to 2.14.0
     add df036a7  SLING-12459 - Redirect sonarcloud notifications to 
[email protected]
     add 8eb5d55  SLING-12730 Update to Parent 62
     add 333f622  Bump commons-io:commons-io from 2.5 to 2.14.0

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   (9782e10)
            \
             N -- N -- N   
refs/heads/dependabot/maven/commons-io-commons-io-2.14.0 (333f622)

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 | 1 +
 pom.xml   | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

Reply via email to