This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.sling-org.apache.sling.engine-2.14.0
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-dynamic-include.git
omit 40abee7 Bump org.apache.sling.engine from 2.2.0 to 2.14.0
add 55f8769 SLING-12094 - Use GitHub for the Maven scm.url value
add f8984be SLING-12459 - Redirect sonarcloud notifications to
[email protected]
add 6f6ce6c [maven-release-plugin] prepare release
org.apache.sling.dynamic-include-3.3.2
add 2dd4ba1 [maven-release-plugin] prepare for next development iteration
add 26baf69 SLING-12654 - Upgrade to parent pom 52 (#28)
add d2c2ddf Bump org.apache.sling.engine from 2.2.0 to 2.14.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 (40abee7)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.sling-org.apache.sling.engine-2.14.0
(d2c2ddf)
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:
.asf.yaml | 1 +
pom.xml | 32 +++++++++++++++++++++++++++-----
2 files changed, 28 insertions(+), 5 deletions(-)
