This is an automated email from the ASF dual-hosted git repository.
hgruszecki pushed a change to branch ci/pin-docker-actions
in repository https://gitbox.apache.org/repos/asf/iggy.git
omit d53a97903 ci(deps): bump bazel-contrib/setup-bazel to v0.18.0
omit 9e5cea561 ci(docker): pin Docker actions to SHA per ASF allowlist
policy
add f762e4f2b feat(server): implement TwoHalves buffer (#2944)
new ffd417b0c ci(docker): pin Docker actions to SHA per ASF allowlist
policy
new e5c30a2c9 ci(deps): bump bazel-contrib/setup-bazel to v0.18.0
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 (d53a97903)
\
N -- N -- N refs/heads/ci/pin-docker-actions (e5c30a2c9)
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.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Cargo.lock | 7 +
Cargo.toml | 1 +
DEPENDENCIES.md | 1 +
core/{clock => iobuf}/Cargo.toml | 10 +-
core/iobuf/src/lib.rs | 604 +++++++++++++++++++++++++++++++++++++++
5 files changed, 616 insertions(+), 7 deletions(-)
copy core/{clock => iobuf}/Cargo.toml (87%)
create mode 100644 core/iobuf/src/lib.rs
