This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/mavenVersion-3.9.11
in repository https://gitbox.apache.org/repos/asf/maven-doap-plugin.git
omit 804799f Bump mavenVersion from 3.6.3 to 3.9.11
add 537924e Add Apache 2.0 LICENSE file
add 3cafc9d feat: enable prevent branch protection rules (#114)
add a807eb3 Bump org.codehaus.plexus:plexus-i18n from 1.0-beta-10 to
1.0.0 (#116)
add 62e79a5 Bump scmVersion from 2.1.0 to 2.2.1
add fcb48e2 Update parent to 45 (#118)
add 2ee2c1e Bump mavenVersion from 3.6.3 to 3.9.11
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 (804799f)
\
N -- N -- N refs/heads/dependabot/maven/mavenVersion-3.9.11
(2ee2c1e)
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:
.asf.yaml | 6 +-
LICENSE | 202 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
pom.xml | 8 ++-
3 files changed, 211 insertions(+), 5 deletions(-)
create mode 100644 LICENSE
