This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/spring.version-5.3.34 in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
discard ed18faa4c1 Bump spring.version from 5.3.33 to 5.3.34 add 874a369ad2 Bump com.github.veithen.maven:jacoco-report-maven-plugin add 31f981f3ee bump activemq.version from 6.1.0 to 6.1.2 add c4e9b99a82 bump org.apache.maven.plugins:maven-jar-plugin from 3.3.0 to 3.4.0 add 3e9bdc4a84 bump slf4j.version from 2.0.12 to 2.0.13 add 9805fd827a Bump spring.version from 5.3.33 to 5.3.34 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 (ed18faa4c1) \ N -- N -- N refs/heads/dependabot/maven/spring.version-5.3.34 (9805fd827a) 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: pom.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)