This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/slf4jVersion-2.0.17
in repository
https://gitbox.apache.org/repos/asf/maven-build-cache-extension.git
omit d190165 Bump slf4jVersion from 1.7.36 to 2.0.17
add b8180b8 Bump org.assertj:assertj-core from 3.27.6 to 3.27.7 (#446)
add dc41937 Use Junit annotations for os select (#454)
add 4a242c9 Bump org.eclipse.sisu:org.eclipse.sisu.plexus from 0.9.0.M4
to 1.0.0
add bd9d68e Bump org.apache.maven.plugins:maven-dependency-plugin (#456)
add 697f01e fix for issue #450 - fixed CacheUtils.unzip to properly
restore unix permissions on file systems that support it (#451)
add 094161d Bump org.junit:junit-bom from 5.14.2 to 5.14.3 (#457)
add f894f4d Bump slf4jVersion from 1.7.36 to 2.0.17
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 (d190165)
\
N -- N -- N refs/heads/dependabot/maven/slf4jVersion-2.0.17
(f894f4d)
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:
pom.xml | 8 ++---
.../org/apache/maven/buildcache/CacheUtils.java | 17 +++++----
.../buildcache/CacheUtilsPermissionsTest.java | 40 +++++++++++++++++-----
3 files changed, 45 insertions(+), 20 deletions(-)
