This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.shared-maven-shared-components-43
in repository https://gitbox.apache.org/repos/asf/maven-archiver.git
omit 4805be1 Bump org.apache.maven.shared:maven-shared-components from 42
to 43
add 43cb230 Bump org.assertj:assertj-core from 3.26.0 to 3.26.3
add 62ac326 use new Reproducible Central badge endpoint
add f756583 [MSHARED-1445] Unix timestamps since the epoch are not
subject to the boundary checks
add ce1437b [MSHARED-1446] Add docs about repro build output timestamp
boundaries
add c7c52c2 Bump org.apache.maven.shared:maven-shared-components from 42
to 43
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 (4805be1)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.shared-maven-shared-components-43
(c7c52c2)
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:
README.md | 2 +-
pom.xml | 2 +-
src/main/java/org/apache/maven/archiver/MavenArchiver.java | 12 ++++++++++--
.../java/org/apache/maven/archiver/MavenArchiverTest.java | 10 +++-------
4 files changed, 15 insertions(+), 11 deletions(-)
