This is an automated email from the ASF dual-hosted git repository.
nfilotto pushed a change to branch fix-component-test-ga-token-exposure
in repository https://gitbox.apache.org/repos/asf/camel.git
omit c837fd8fede use git submodules
omit a58909e3d3c use the git hash instead of the version
omit f24b56d297e use create-or-update-comment
omit a1de7aeb2f6 (chore) ci: avoid token exposure in pr-comment workflow
add 54f4a8ef442 Upgrade AWS SDK v2 to version 2.21.13 (#11883)
add 023466f13b2 Upgrade Flink to version 1.18.0 (#11884)
add 4f5564fff16 (chore) ci: add github action create-or-update-comment
(#11886)
add 13585283d94 (chore) ci: avoid token exposure in pr-comment workflow
add cdd465c535f use create-or-update-comment
add 5e50eb548cc use the git hash instead of the version
add 17b385ae1a0 use the local github action create-or-update-comment
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 (c837fd8fede)
\
N -- N -- N refs/heads/fix-component-test-ga-token-exposure
(17b385ae1a0)
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:
parent/pom.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
