This is an automated email from the ASF dual-hosted git repository.
royteeuwen pushed a change to branch bugfix/SLING-13134
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-committer-cli.git
discard 08643ce Specifically pin to SLF4J 1.x so that it doesn't affect the
feature model used by this project, which wouldn't run with SLF4J 2.x
discard d99a56c Update project to compile on Java 24
discard cbf4df8 Upgrade to latest parent and do a spotless apply
add 1066ba5 Update to latest parent pom and Java 21
add b7614a1 Execute spotless:apply
add a32550b Ignore spotless apply in git blame
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 (08643ce)
\
N -- N -- N refs/heads/bugfix/SLING-13134 (a32550b)
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:
.git-blame-ignore-revs | 1 +
.sling-module.json | 2 +-
Dockerfile | 2 +-
pom.xml | 2 +-
.../cli/impl/release/TallyVotesCommandTest.java | 36 +++++++++++-----------
5 files changed, 22 insertions(+), 21 deletions(-)
create mode 100644 .git-blame-ignore-revs
