This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch azurite-3.27.0
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 23f66efa371 Upgrade Azurite container image to version 3.27.0
add 4f5564fff16 (chore) ci: add github action create-or-update-comment
(#11886)
add 26abaf076b7 CAMEL-20069 - Upgrade Azure SDK BOM to version 1.2.18
(#11885)
add 28fd75aa18d (chore) ci: avoid token exposure in pr-comment workflow
(#11880)
new 690e825b5ee Upgrade Azurite container image to version 3.27.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 (23f66efa371)
\
N -- N -- N refs/heads/azurite-3.27.0 (690e825b5ee)
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 1 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:
.github/actions/component-test/action.yaml | 35 +++++++++---------------------
.github/actions/create-or-update-comment | 1 +
.github/workflows/pr-comment.yml | 15 +++++--------
.gitmodules | 3 +++
parent/pom.xml | 2 +-
5 files changed, 20 insertions(+), 36 deletions(-)
create mode 160000 .github/actions/create-or-update-comment
