[myfaces-tobago] branch dependabot/npm_and_yarn/tobago-example/tobago-example-demo/npm/rollup-2.40.0 updated (42c79f8 -> 6abcc0b)

[gi...@apache.org]

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

github-bot pushed a change to branch dependabot/npm_and_yarn/tobago-example/tobago-example-demo/npm/rollup-2.40.0
in repository https://gitbox.apache.org/repos/asf/myfaces-tobago.git.


 discard 42c79f8  chore(deps-dev): bump rollup in /tobago-example/tobago-example-demo/npm
     add 13101ca  chore(deps): bump jetty-maven-plugin
     add 4a2bf89  chore(deps): bump joinfaces.version from 4.4.2 to 4.4.3
     add c962f66  chore(deps-dev): bump eslint in /tobago-theme/tobago-theme-standard/npm
     add 383fc18  chore(deps-dev): bump rollup in /tobago-theme/tobago-theme-standard/npm
     add 6abcc0b  chore(deps-dev): bump rollup in /tobago-example/tobago-example-demo/npm

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   (42c79f8)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/tobago-example/tobago-example-demo/npm/rollup-2.40.0 (6abcc0b)

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:
 tobago-example/pom.xml                             |   2 +-
 tobago-example/tobago-example-spring-boot/pom.xml  |   2 +-
 .../tobago-theme-standard/npm/package-lock.json    | 105 +++++++++------------
 .../tobago-theme-standard/npm/package.json         |   4 +-
 4 files changed, 46 insertions(+), 67 deletions(-)