This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/org.apache.maven.shared-maven-dependency-tree-3.1.0 in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git.
discard d71c18d Bump maven-dependency-tree from 3.0.1 to 3.1.0 add c8ac026 Bump doxia-site-renderer from 1.9.2 to 1.10 (#142) add f3c20f8 Bump asm from 9.1 to 9.2 (#141) add a28c4b8 Bump doxiaVersion from 1.9.1 to 1.10 (#139) add f82b50e Use absolute URL for Dependency Mechanism link (#140) add 2caed76 Fix source repo link add 84cba60 update CI url add 9bb14b4 add gh actions add 8165e72 Bump maven-dependency-tree from 3.0.1 to 3.1.0 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 (d71c18d) \ N -- N -- N refs/heads/dependabot/maven/org.apache.maven.shared-maven-dependency-tree-3.1.0 (8165e72) 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: .github/workflows/maven.yml | 54 ++++++++++++++++++++++ README.md | 8 ++-- pom.xml | 6 +-- .../examples/copying-project-dependencies.apt.vm | 2 +- src/site/apt/index.apt.vm | 4 +- src/site/site.xml | 2 +- 6 files changed, 65 insertions(+), 11 deletions(-) create mode 100644 .github/workflows/maven.yml