This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/maven-jar-plugin-3.x/commons-io-commons-io-2.18.0
in repository https://gitbox.apache.org/repos/asf/maven-jar-plugin.git
discard b5fd4b3 Bump commons-io:commons-io from 2.16.1 to 2.18.0
add 08cea8e [MNGSITE-529] Rename "Goals" to "Plugin Documentation"
add 872bef1 Fix for Maven 4.0.0-rc-3
add 4466b47 Improve release-drafter configuration
add b633da3 Add PR Automation to 3.x
add e079ed7 Bump org.codehaus.plexus:plexus-archiver from 4.9.2 to 4.10.0
(#109)
add 2ca1407 Bump commons-io:commons-io from 2.16.1 to 2.18.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 (b5fd4b3)
\
N -- N -- N
refs/heads/dependabot/maven/maven-jar-plugin-3.x/commons-io-commons-io-2.18.0
(2ca1407)
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:
.../{release-drafter.yml => pr-automation.yml} | 17 ++++++++---------
.github/workflows/release-drafter.yml | 6 +++++-
pom.xml | 19 ++++++++-----------
src/site/site.xml | 2 +-
4 files changed, 22 insertions(+), 22 deletions(-)
copy .github/workflows/{release-drafter.yml => pr-automation.yml} (80%)
