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-45
in repository https://gitbox.apache.org/repos/asf/maven-jdeprscan-plugin.git
omit 8aa4285 Bump org.apache.maven.plugins:maven-plugins from 43 to 45
add 8348bd3 Remove Jira Link (#52)
add 6e9235f Bump org.apache.commons:commons-lang3 from 3.17.0 to 3.18.0
(#53)
add 9dd4815 Add Apache 2.0 LICENSE file
add e73331b Bump actions/setup-java from 4 to 5
add b08b9b8 Bump actions/checkout from 4 to 5
add 38d896e feat: enable prevent branch protection rules
add 1e26c38 Bump org.apache.commons:commons-lang3 from 3.18.0 to 3.19.0
add e369280 Bump org.apache.maven.plugins:maven-plugins from 43 to 45
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 (8aa4285)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.plugins-maven-plugins-45 (e369280)
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 +-
.github/ISSUE_TEMPLATE/config.yml | 4 -
.github/workflows/maven.yaml | 6 +-
LICENSE | 202 ++++++++++++++++++++++++++++++++++++++
pom.xml | 2 +-
5 files changed, 210 insertions(+), 10 deletions(-)
create mode 100644 LICENSE
