This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/commons-io-commons-io-2.7 in repository https://gitbox.apache.org/repos/asf/maven-remote-resources-plugin.git
discard e686177 Bump commons-io from 2.6 to 2.7 add cbba521 [maven-release-plugin] prepare release maven-remote-resources-plugin-3.0.0 add f85e1d6 [maven-release-plugin] prepare for next development iteration add ba232fc Fix site "usage" page (#8) add af2c579 run build only with maven '3.6.x' and '3.8.x' add 0281f0a Merge pull request #9 from apache/maven-run-only-3.6.x-3.8.x add 7d27388 typo add 27d395a Bump commons-io from 2.6 to 2.7 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 (e686177) \ N -- N -- N refs/heads/dependabot/maven/commons-io-commons-io-2.7 (27d395a) 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: Jenkinsfile | 2 +- pom.xml | 9 ++++++--- 2 files changed, 7 insertions(+), 4 deletions(-)