This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/mvnd-1.x/org.graalvm.nativeimage-svm-25.0.0
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git
discard a47a109c Bump org.graalvm.nativeimage:svm from 24.2.2 to 25.0.0
add 824a1fd4 [release] Release 1.0.3
add 53c06584 Next is 1.0.4-SNAPSHOT
add 49573ccf Bump org.assertj:assertj-core from 3.27.4 to 3.27.5 (#1437)
add eb6c24e1 Bump org.apache.maven.plugins:maven-javadoc-plugin from
3.11.3 to 3.12.0 (#1441)
add 32796307 Bump org.assertj:assertj-core from 3.27.5 to 3.27.6 (#1443)
add 14a481b0 Bump org.graalvm.buildtools:native-maven-plugin from 0.11.0
to 0.11.1
add 4aad7494 Bump org.graalvm.nativeimage:svm from 24.2.2 to 25.0.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 (a47a109c)
\
N -- N -- N
refs/heads/dependabot/maven/mvnd-1.x/org.graalvm.nativeimage-svm-25.0.0
(4aad7494)
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:
agent/pom.xml | 2 +-
build-plugin/pom.xml | 2 +-
client/pom.xml | 2 +-
common/pom.xml | 2 +-
daemon/pom.xml | 2 +-
dist/pom.xml | 2 +-
helper/pom.xml | 2 +-
integration-tests/pom.xml | 2 +-
logging/pom.xml | 2 +-
native/pom.xml | 2 +-
pom.xml | 10 +++++-----
11 files changed, 15 insertions(+), 15 deletions(-)
