This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/slf4j.version-2.0.2
in repository https://gitbox.apache.org/repos/asf/commons-configuration.git
discard a1081b56 Bump slf4j.version from 2.0.1 to 2.0.2
add 312c44a2 Bump junit-jupiter from 5.9.0 to 5.9.1 (#217)
add d7820d57 Bump junit-jupiter from 5.9.0 to 5.9.1 #217
add 7f63386c Bump commons-parent from 53 to 54 (#216)
add 5b2f9e74 Bump commons-parent from 53 to 54 #216
add 20c84c0e Bump log4j.version from 2.18.0 to 2.19.0 (#213)
add 6154bba7 Bump slf4j.version from 2.0.1 to 2.0.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 (a1081b56)
\
N -- N -- N refs/heads/dependabot/maven/slf4j.version-2.0.2
(6154bba7)
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:
pom.xml | 6 +++---
src/changes/changes.xml | 5 ++++-
2 files changed, 7 insertions(+), 4 deletions(-)
