This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/org.apache.maven.plugins-maven-plugins-39 in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git
discard 2bd31dec Bump maven-plugins from 38 to 39 add 4b478d61 [MDEP-841] Explicitly start and end tables with Doxia Sinks in report renderers add 520f8fd6 [maven-release-plugin] prepare release maven-dependency-plugin-3.5.0 add b822663b [maven-release-plugin] prepare for next development iteration add 455edc14 Bump maven-plugins from 38 to 39 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 (2bd31dec) \ N -- N -- N refs/heads/dependabot/maven/org.apache.maven.plugins-maven-plugins-39 (455edc14) 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 | 10 +++++----- .../maven/plugins/dependency/analyze/AnalyzeReportView.java | 2 ++ 2 files changed, 7 insertions(+), 5 deletions(-)