This is an automated email from the ASF dual-hosted git repository.
hubcio pushed a change to branch server-ng-pr4-spine-mechanisms
in repository https://gitbox.apache.org/repos/asf/iggy.git
omit eb1ef8d68 fix(server): close fail-open replies and the shard-0 writer
race
omit c80100941 fix(server): deny malformed consumer-group requests instead
of dropping
omit 02c823e5d refactor(server): make dispatch routing and failure paths
explicit
add 7f0bc26d1 chore(deps): Bump the node group across 2 directories with 3
updates (#4052)
add 02f844f4c chore(deps): Bump the web group across 1 directory with 3
updates (#4051)
add 8963ca434 refactor(server): make dispatch routing and failure paths
explicit
add 5538c2171 fix(server): deny malformed consumer-group requests instead
of dropping
add 1591afabb fix(server): close fail-open replies and the shard-0 writer
race
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 (eb1ef8d68)
\
N -- N -- N refs/heads/server-ng-pr4-spine-mechanisms (1591afabb)
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:
examples/node/package-lock.json | 8 +--
examples/node/package.json | 2 +-
foreign/node/package-lock.json | 142 ++++++++++++++++++++--------------------
foreign/node/package.json | 2 +-
web/package-lock.json | 140 +++++++++++++++++++--------------------
web/package.json | 6 +-
6 files changed, 150 insertions(+), 150 deletions(-)
