This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-10231
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-starter.git
discard 7f3b5ba SLING-12031 - Allow auto-launch of Java agents for the
container image
omit 5499806 Exclude the xmlParserAPIs dependency from the classpath
add 66a4752 chore(deps): update actions/checkout action to v4 (#229)
add ee7eb41 Exclude the xmlParserAPIs dependency from the classpath (#230)
add 2dc5dd1 chore(deps): update docker/login-action action to v3 (#231)
add e5da3bd chore(deps): update docker/setup-buildx-action action to v3
(#232)
add f4939f7 chore(deps): update docker/setup-qemu-action action to v3
(#233)
new 183a390 SLING-12031 - Allow auto-launch of Java agents for the
container image
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 (7f3b5ba)
\
N -- N -- N refs/heads/issue/SLING-10231 (183a390)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/workflows/docker-push.yml | 8 ++++----
.github/workflows/docker-release.yml | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
