[myfaces-tobago] branch dependabot/npm_and_yarn/tobago-example/tobago-example-demo/rollup-2.48.0 updated (40577ad -> 28d3898)

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


 discard 40577ad  build(deps-dev): bump rollup in /tobago-example/tobago-example-demo
     add 10f3879  build(deps): bump frontend-maven-plugin from 1.11.3 to 1.12.0
     add c475b6e  build(deps-dev): bump junit-jupiter-params from 5.7.1 to 5.7.2
     add bc83f20  build(deps-dev): bump junit-jupiter-api from 5.7.1 to 5.7.2
     add dd695be  build(deps-dev): bump junit-jupiter-engine from 5.7.1 to 5.7.2
     add b6068d9  build(deps-dev): bump @typescript-eslint/eslint-plugin in /tobago-theme
     add 28d3898  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   (40577ad)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/tobago-example/tobago-example-demo/rollup-2.48.0 (28d3898)

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                        |  8 +++---
 tobago-theme/package-lock.json | 56 +++++++++++++++++++++---------------------
 tobago-theme/package.json      |  2 +-
 3 files changed, 33 insertions(+), 33 deletions(-)