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

github-bot pushed a change to branch 
dependabot/maven/com.sun.xml.bind-jaxb-impl-3.0.2
in repository https://gitbox.apache.org/repos/asf/commons-scxml.git.


 discard 2bf2ca9  Bump jaxb-impl from 2.3.6 to 3.0.2
     add 33ca39f  Bump Saxon-HE from 9.6.0-1 to 11.2 #42
     add c177534  Bump Saxon-HE from 9.6.0-1 to 11.2
     add 1e61912  Merge pull request #42 from 
apache/dependabot/maven/net.sf.saxon-Saxon-HE-11.2
     add b976f98  Merge branch 'master' of 
https://gitbox.apache.org/repos/asf/commons-scxml.git
     add 5134df9  Bump jackson-core from 2.9.3 to 2.13.2
     add 6ba9805  Merge pull request #39 from 
apache/dependabot/maven/com.fasterxml.jackson.core-jackson-core-2.13.2
     add e6c43c8  Bump jackson-core from 2.9.3 to 2.13.2 #39
     add 1b4e96d  Bump junit-jupiter-engine from 5.4.2 to 5.8.2
     add d39d4e8  Merge pull request #40 from 
apache/dependabot/maven/org.junit.jupiter-junit-jupiter-engine-5.8.2
     add ef5b882  Bump junit-jupiter-engine from 5.4.2 to 5.8.2 #40
     add 7f26288  Bump jaxb-impl from 2.3.6 to 3.0.2

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   (2bf2ca9)
            \
             N -- N -- N   
refs/heads/dependabot/maven/com.sun.xml.bind-jaxb-impl-3.0.2 (7f26288)

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:
 pom.xml                 | 6 +++---
 src/changes/changes.xml | 4 ++++
 2 files changed, 7 insertions(+), 3 deletions(-)

Reply via email to