[myfaces-tobago] branch dependabot/npm_and_yarn/tobago-theme/jest-and-types/jest-29.1.2 updated (566bc315a0 -> d4b55dad69)

[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-theme/jest-and-types/jest-29.1.2
in repository https://gitbox.apache.org/repos/asf/myfaces-tobago.git


 discard 566bc315a0 build(deps-dev): bump jest and @types/jest in /tobago-theme
     add dcaee3ed27 build(deps-dev): bump ts-jest from 29.0.1 to 29.0.3 in /tobago-theme
     add 5111e43d55 build(deps-dev): bump @typescript-eslint/eslint-plugin in /tobago-theme
     add 0a517d5287 build(deps-dev): bump postcss from 8.4.16 to 8.4.17 in /tobago-theme
     add f414e13ce1 build(deps-dev): bump sass in /tobago-example/tobago-example-demo
     add d4b55dad69 build(deps-dev): bump jest and @types/jest in /tobago-theme

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   (566bc315a0)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/tobago-theme/jest-and-types/jest-29.1.2 (d4b55dad69)

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          |  14 +-
 tobago-example/tobago-example-demo/package.json    |   2 +-
 tobago-theme/package-lock.json                     | 380 ++++++++++++++++++---
 tobago-theme/package.json                          |   6 +-
 4 files changed, 342 insertions(+), 60 deletions(-)