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.24.2 in repository https://gitbox.apache.org/repos/asf/maven-jlink-plugin.git
discard fc04aa5 Bump assertj-core from 3.21.0 to 3.24.2 add d9a31d1 Bump maven-javadoc-plugin from 3.3.1 to 3.5.0 add aa76ec7 (doc) cleanup toolchain setup add 0144312 Bump junit-bom from 5.8.2 to 5.9.2 add 736d801 Bump assertj-core from 3.21.0 to 3.24.2 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 (fc04aa5) \ N -- N -- N refs/heads/dependabot/maven/org.assertj-assertj-core-3.24.2 (736d801) 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: .github/workflows/maven.yml | 41 +++++++---------------------------------- pom.xml | 4 ++-- 2 files changed, 9 insertions(+), 36 deletions(-)