This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/spring-boot.version-3.4.4
in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git
discard 6f89a857a Bump spring-boot.version from 3.3.5 to 3.4.4
add 9046e157b Bump com.puppycrawl.tools:checkstyle from 10.21.3 to 10.22.0
(#4760)
add 436d3e0e3 Bump io.swagger.core.v3:swagger-core-jakarta from 2.2.28 to
2.2.29 (#4759)
add 8dc46def1 Bump org.junit:junit-bom from 5.12.0 to 5.12.1 (#4758)
add 74e2b280a Bump spring-boot.version from 3.3.5 to 3.4.4
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 (6f89a857a)
\
N -- N -- N
refs/heads/dependabot/maven/spring-boot.version-3.4.4 (74e2b280a)
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:
dependencies/default/pom.xml | 4 ++--
pom.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
