This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/jira-rest-client-api-version-6.0.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 15ddbf8e697 chore(deps): Bump jira-rest-client-api-version from 5.2.7
to 6.0.1
add f51c19ed169 chore(deps): Bump huaweicloud-sdk-version from 3.1.104 to
3.1.105 (#14791)
add 302d3a6d04c chore(deps): Bump com.squareup:kotlinpoet-jvm from 1.17.0
to 1.18.0 (#14795)
add 433f2b9c541 chore(deps): Bump
com.google.auth:google-auth-library-oauth2-http (#14799)
add 617119e55af chore(deps): Bump com.slack.api:slack-api-client from
1.40.1 to 1.40.2 (#14794)
add 235e3267ffb chore(deps): Bump org.jgroups:jgroups from 5.3.7.Final to
5.3.8.Final (#14797)
add dbf96b33382 chore(deps): Bump maven-surefire-plugin-version from 3.3.0
to 3.3.1 (#14800)
add fb2d511192b chore(deps): Bump jira-rest-client-api-version from 5.2.7
to 6.0.1
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 (15ddbf8e697)
\
N -- N -- N
refs/heads/dependabot/maven/jira-rest-client-api-version-6.0.1 (fb2d511192b)
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 | 10 +++++-----
pom.xml | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
