[myfaces-tobago] branch dependabot/npm_and_yarn/tobago-example/tobago-example-demo/rollup-3.9.1 updated (79608e3000 -> 60c7c4c413)

[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/rollup-3.9.1
in repository https://gitbox.apache.org/repos/asf/myfaces-tobago.git


 discard 79608e3000 build(deps-dev): bump rollup in /tobago-example/tobago-example-demo
     add c0959eb7d9 build(deps-dev): bump @rollup/plugin-commonjs in /tobago-theme
     add bc1c21d706 build(deps-dev): bump @rollup/plugin-replace
     add 6c7aed0ff6 build(deps-dev): bump @types/jest from 29.2.4 to 29.2.5 in /tobago-theme
     add 60c7c4c413 build(deps-dev): bump rollup in /tobago-example/tobago-example-demo

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   (79608e3000)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/tobago-example/tobago-example-demo/rollup-3.9.1 (60c7c4c413)

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-demo/package-lock.json          | 58 +++++++++++-----------
 tobago-example/tobago-example-demo/package.json    |  2 +-
 tobago-theme/package-lock.json                     | 53 ++++++++++++++------
 tobago-theme/package.json                          |  4 +-
 4 files changed, 69 insertions(+), 48 deletions(-)