This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/spring.version-6.1.6
in repository https://gitbox.apache.org/repos/asf/commons-configuration.git
discard 7009eff4 Bump spring.version from 5.3.33 to 6.1.6
add 55f1e380 Bump codecov/codecov-action from 4.2.0 to 4.3.0 (#401)
add 40eed878 Bump slf4j.version from 2.0.12 to 2.0.13 (#403)
add 2427aacf Bump slf4j.version from 2.0.12 to 2.0.13 #403
add 04fbb072 Bump org.apache.commons:commons-text from 1.11.0 to 1.12.0
(#404)
add abbfa243 Bump org.apache.commons:commons-text from 1.11.0 to 1.12.0
#404
add 4ffe2da6 Bump spring.version from 5.3.33 to 5.3.34
add c4d3c407 Bump spring.version from 5.3.33 to 6.1.6
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 (7009eff4)
\
N -- N -- N refs/heads/dependabot/maven/spring.version-6.1.6
(c4d3c407)
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:
.github/workflows/coverage.yml | 2 +-
pom.xml | 4 ++--
src/changes/changes.xml | 3 +++
3 files changed, 6 insertions(+), 3 deletions(-)
