This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/groovy-version-3.0.10
in repository https://gitbox.apache.org/repos/asf/camel-k-runtime.git.
discard a0c0a16 build(deps): bump groovy-version from 3.0.9 to 3.0.10
add db54e02 build(deps): bump maven-plugin-annotations from 3.6.2 to 3.6.4
add b2ee274 Updated CHANGELOG.md
add 74e70f1 build(deps): bump versions-maven-plugin from 2.9.0 to 2.10.0
add b016668 build(deps): bump spock-core from 2.0-groovy-3.0 to
2.1-groovy-3.0
add 9fb9ee6 build(deps): bump groovy-version from 3.0.9 to 3.0.10
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 (a0c0a16)
\
N -- N -- N refs/heads/dependabot/maven/groovy-version-3.0.10
(9fb9ee6)
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:
CHANGELOG.md | 1 +
pom.xml | 6 +++---
2 files changed, 4 insertions(+), 3 deletions(-)
