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

dependabot[bot] pushed a change to branch dependabot/npm_and_yarn/js-yaml-4.3.1
in repository https://gitbox.apache.org/repos/asf/incubator-kie-tools.git


    omit b0930657667 build(deps): bump js-yaml from 4.3.0 to 4.3.1
     add fc75ba0fd85 NO-ISSUE: Add X-Content-Type-Options header to Extended 
Services responses (#3988)
     add fd475da2204 [NO-ISSUE]: Fixed CI issue related to pnpm setup (#3991)
     add 122e2cbe7b3 NO-ISSUE: Fix BPMN and DMN editors never loading in the VS 
Code extension (#3989)
     add 4aef4a795a1 [NO-ISSUE] Update fast-uri to 3.1.7 (#3990)
     add 1f93fb4ac75 build(deps): bump js-yaml from 4.3.0 to 4.3.1

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   (b0930657667)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/js-yaml-4.3.1 
(1f93fb4ac75)

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:
 .github/actions/setup-env/action.yml               |   9 +-
 .github/workflows/ci_build.yml                     |   9 +-
 .../src/main/resources/application.properties      |   1 +
 .../test/java/org/kie/tools/PingResourceTest.java  |   1 +
 .../VsCodeResourceContentServiceIsomorphicGitFs.ts |  14 ++
 pnpm-lock.yaml                                     | 174 +++++++++++----------
 6 files changed, 119 insertions(+), 89 deletions(-)


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

Reply via email to