This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/org.codehaus.plexus-plexus-archiver-4.10.0 in repository https://gitbox.apache.org/repos/asf/maven-plugin-tools.git
discard d398750b Bump org.codehaus.plexus:plexus-archiver from 4.9.2 to 4.10.0 add 6aded70c Bump org.junit:junit-bom from 5.10.2 to 5.10.3 add 568bc4bc Bump net.bytebuddy:byte-buddy from 1.14.17 to 1.14.18 add d134a275 Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 add a13f5267 Bump org.codehaus.plexus:plexus-archiver from 4.9.2 to 4.10.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 (d398750b) \ N -- N -- N refs/heads/dependabot/maven/org.codehaus.plexus-plexus-archiver-4.10.0 (a13f5267) 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: maven-plugin-tools-annotations/pom.xml | 2 +- pom.xml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)