This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/logback.version-1.5.3
in repository https://gitbox.apache.org/repos/asf/commons-logging.git
discard 8aba777 Bump logback.version from 1.3.12 to 1.5.3
add c8a072c Bump org.apache.commons:commons-parent from 66 to 67 (#225)
add 1c2bea0 Bump org.apache.commons:commons-parent from 66 to 67 #225
add 19763ed Bump actions/setup-java from 4.1.0 to 4.2.1 (#227)
add c8de36c Bump github/codeql-action from 3.24.6 to 3.24.7 (#228)
add dc7821c Bump actions/checkout from 4.1.1 to 4.1.2 (#226)
add 71f4304 Upgrade `log4j-api` to version `2.23.1` (#230)
add 63c5838 Bump logback.version from 1.3.12 to 1.5.3
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 (8aba777)
\
N -- N -- N refs/heads/dependabot/maven/logback.version-1.5.3
(63c5838)
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/codeql-analysis.yml | 8 +++----
.github/workflows/coverage.yml | 4 ++--
.github/workflows/maven.yml | 4 ++--
.github/workflows/scorecards-analysis.yml | 4 ++--
pom.xml | 38 +++++++++++++++++++++++++++++--
src/changes/changes.xml | 4 ++--
6 files changed, 48 insertions(+), 14 deletions(-)
