[myfaces-tobago] branch dependabot/maven/tobago-5.x/com.google.guava-guava-32.1.1-jre updated (c8dee46eb9 -> 0bdf95b650)

[gi...@apache.org]

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

github-bot pushed a change to branch dependabot/maven/tobago-5.x/com.google.guava-guava-32.1.1-jre
in repository https://gitbox.apache.org/repos/asf/myfaces-tobago.git


 discard c8dee46eb9 build(deps): bump guava from 32.0.1-jre to 32.1.1-jre
     add e1bd25502d chore: update checkstyle-rules
     add 2aa7d4b997 chore(deps): update Tomcat for Spring
     add 296dea6676 chore(deps): update NPM dependencies
     add 0bdf95b650 build(deps): bump guava from 32.0.1-jre to 32.1.1-jre

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   (c8dee46eb9)
            \
             N -- N -- N   refs/heads/dependabot/maven/tobago-5.x/com.google.guava-guava-32.1.1-jre (0bdf95b650)

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                                            |   4 +-
 .../tobago-example-demo/package-lock.json          |  42 +--
 tobago-example/tobago-example-demo/package.json    |   6 +-
 tobago-theme/package-lock.json                     | 400 ++++++++++-----------
 tobago-theme/package.json                          |  18 +-
 5 files changed, 235 insertions(+), 235 deletions(-)