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

dependabot[bot] pushed a change to branch 
dependabot/npm_and_yarn/drools-docs/multi-ae990f0b0b
in repository https://gitbox.apache.org/repos/asf/incubator-kie-docs.git


 discard f431f3427 Bump js-yaml, @antora/cli and @antora/site-generator in 
/drools-docs
     add 19960fde0 [incubator-kie#7133] Update drools docs about sequential 
mode (#4600)
     add 2ab3c6777 [incubator-kie#7132] Clarify that insert(Object object, 
boolean dynam… (#4601)
     add 9e0d42bbe Bump handlebars from 4.7.9 to 4.7.10 in /drools-docs (#4602)
     add 3603e776f Bump brace-expansion from 1.1.16 to 1.1.21 in /drools-docs 
(#4603)
     add e03079f27 Bump js-yaml, @antora/cli and @antora/site-generator in 
/drools-docs

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   (f431f3427)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/drools-docs/multi-ae990f0b0b (e03079f27)

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:
 drools-docs/package-lock.json                      | 364 ++++++++++-----------
 drools-docs/package.json                           |   4 +-
 .../rule-engine/_phreak-sequential-mode-con.adoc   |  32 +-
 .../_property-change-listeners-con.adoc            |  45 ++-
 4 files changed, 232 insertions(+), 213 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to