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.9.2 in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git
discard a0346f11 Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 add 08f16379 Bump apache/maven-gh-actions-shared from 3 to 4 add dbb5e484 [MJAVADOC-788] Bump commons-io:commons-io from 2.15.1 to 2.16.0 (#273) add 0b7d8dbe [MJAVADOC-789] Bump org.codehaus.plexus:plexus-interactivity-api from 1.2 to 1.3 (#268) add ded56a90 Exclude JDK 8 - temurin, adopt-openj9 on macos add 68ec0b5f Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.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 (a0346f11) \ N -- N -- N refs/heads/dependabot/maven/org.codehaus.plexus-plexus-archiver-4.9.2 (68ec0b5f) 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 | 5 +++-- .github/workflows/release-drafter.yml | 2 +- pom.xml | 14 ++------------ 3 files changed, 6 insertions(+), 15 deletions(-)