This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/org.assertj-assertj-core-3.25.1 in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git
discard c3348e39 Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 add 53ea2cf8 Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 add 3411c5fe Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1 add 7d128702 Revert "Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2" add 69cbe479 Revert "Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1" add 713342c2 Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 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 (c3348e39) \ N -- N -- N refs/heads/dependabot/maven/org.assertj-assertj-core-3.25.1 (713342c2) 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: